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?
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?
Thanks
-------- Forwarded Message --------
Subject: Re: [GIT PULL] PCI changes for v5.12
Date: Wed, 24 Feb 2021 11:21:44 -0800
From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
To: Bjorn Helgaas <helgaas@xxxxxxxxxx>
CC: Linux PCI <linux-pci@xxxxxxxxxxxxxxx>, Linux Kernel Mailing List
<linux-kernel@xxxxxxxxxxxxxxx>, Lorenzo Pieralisi
<lorenzo.pieralisi@xxxxxxx>
On Wed, Feb 24, 2021 at 11:03 AM Bjorn Helgaas <helgaas@xxxxxxxxxx> wrote:
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/pci-v5.12-changes
I pulled this, but I'm now unpulling it again.
Why are many of those commits only two hours old, and most of the rest
is from yesterday?
Has any of this been in linux-next?
And if it has, then why was it rebased, and why didn't you explain
*why* it was rebased if so?
I'm willing to pull this if it turns out it _has_ been in linux-next,
but I need explanations.
Linus
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
