All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: wuzhouhui <wuzhouhui14@mails.ucas.ac.cn>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Fwd: Re: [GIT PULL] PCI changes for v5.12
Date: Fri, 26 Feb 2021 08:07:11 +0100	[thread overview]
Message-ID: <YDieH+Lc2ZSVHMMC@kroah.com> (raw)
In-Reply-To: <eca64c53-3d2f-e3ef-fe4a-178b21e0e537@mails.ucas.ac.cn>

On Fri, Feb 26, 2021 at 12:54:16PM +0800, wuzhouhui wrote:
> I'm confused about what the Linus said. It seemed that the branch cannot
> be rebased after merged into linux-next under normal circumstances, why?

You should never rebase a public-facing branch.

> Linus found this issue by check commit time of commits, but I also found so
> many commit in mainline are too young to be merged into linux-next before
> merge to mainline. If the rebase is not recommended, why people like to
> do rebase after commits are merged into linux-next?

What commits have you found, and are you sure those are not just merged
through email submissions to Linus instead of a git tree pull?  Please
note that some subsystems still use email, like Andrew Morton's.

As for why people like to rebase, I do not know, you will have to ask
them why they like to do bad things :)

does this help?

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2021-02-26  7:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24 19:03 [GIT PULL] PCI changes for v5.12 Bjorn Helgaas
2021-02-24 19:21 ` Linus Torvalds
2021-02-24 21:40   ` Bjorn Helgaas
2021-02-26  4:54   ` Fwd: " wuzhouhui
2021-02-26  7:07     ` Greg KH [this message]
2021-02-26 10:02       ` wuzhouhui
2021-02-26 10:09         ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YDieH+Lc2ZSVHMMC@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=wuzhouhui14@mails.ucas.ac.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.