3 messages, 2 authors, 2012-05-22 · open the first message on its own page
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: 2012-05-22 01:51:23
Folks, bad news ... my fault. I accidentally forgot a --signoff on a git am command last week, meaning that a pair of patches are in -next and not signed off by me. For various (legal) reasons that cannot go into Linus tree as-is, so I have to rebase the tree to fix it. Sorry about that ... Cheers, Ben.
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: 2012-05-22 04:41:07
On Tue, 2012-05-22 at 11:51 +1000, Benjamin Herrenschmidt wrote:
Folks, bad news ... my fault. I accidentally forgot a --signoff on a git am command last week, meaning that a pair of patches are in -next and not signed off by me. For various (legal) reasons that cannot go into Linus tree as-is, so I have to rebase the tree to fix it. Sorry about that ...
Note that the rebase only affects the top 3 commits, so if your tree is based on something older you're fine (Kumar, you seem to be ok, I haven't checked Josh). Cheers, Ben.
From: Josh Boyer <hidden>
Date: 2012-05-22 11:03:40
On Tue, May 22, 2012 at 12:40 AM, Benjamin Herrenschmidt [off-list ref] wrote:
On Tue, 2012-05-22 at 11:51 +1000, Benjamin Herrenschmidt wrote:quoted
Folks, bad news ... my fault. I accidentally forgot a --signoff on a git am command last week, meaning that a pair of patches are in -next and not signed off by me. For various (legal) reasons that cannot go into Linus tree as-is, so I have to rebase the tree to fix it. Sorry about that ...Note that the rebase only affects the top 3 commits, so if your tree is based on something older you're fine (Kumar, you seem to be ok, I haven't checked Josh).
Should be fine. Even if not, all 4 of its users will manage to cope. josh