On Mon, 2013-03-04 at 16:43 +0400, Sergei Shtylyov wrote:
>
> > 3.7 is end-of-life, why would a patch that is already in 3.8, show up in
> > a 3.9-rc1 merge?
>
> Looks like it got into Linus' tree thru 2 different trees: David
> Woodhouse's one (in 3.8) and Artem Bityutsky's one (in 3.9-rc1). I'm indeed
> seeing two commits in Linus' tree now. I'm adding Artem to CC.
Yes. I'd sent it to Linus for 3.8, but Artem had it in his for-3.9 tree
already and didn't ever rebase onto 3.8 after it was released, during
the last merge window. So there's a harmless duplicate commit.
Harmless except for confusing Greg, that is... :)
Normally I go through Artem's tree and filter it a little bit and make
some changes, and end up rebasing it as I go. This time I just asked
Linus to pull Artem's tree directly, hence it actually mattering for
once.
--
Sent with MeeGo's ActiveSync support.
David Woodhouse Open Source Technology Centre
David.Woodhouse@xxxxxxxxx Intel Corporation
Attachment:
smime.p7s
Description: S/MIME cryptographic signature