On Tue, 2007-06-12 at 21:54 -0400, Jeff Garzik wrote: > Michael Ellerman wrote: > > Linas posted the patches, I responded querying whether the bug fixes > > should go into 2.6.22, and then you told him "you need to order your bug > > fixes first in the queue". Which seemed pretty clear to me that you'd > > wait for the reordered series. > > This was presuming Linas actually knew what he himself had submitted > previously, and had been accepted... > > I explicitly emailed Linas on May 24, 2007 detailing each patch that had > been applied, and to which netdev-2.6.git branch it had been applied > (and thus whether it was queued for 2.6.22 or 2.6.23). Relevant > Message-id is <[EMAIL PROTECTED]>, and was sent not only to > Linas but also to netdev@vger.kernel.org, [EMAIL PROTECTED], and > [EMAIL PROTECTED] > > These changes were subsequently made public immediately via > git://git.kernel.org/.../jgarzik/netdev-2.6.git branches > 'upstream-fixes' and 'upstream', and were followed a few days later by > akpm's public tree, starting with 2.6.22-rc3-mm1 (and all subsequent > releases). > > All of the above seemed pretty clear, too.
Yeah fair enuf, that's fairly clear. > To move forward, it sounds like the best thing to do is drop all > spidernet patches and start over, yes? Well see what Linas thinks, but that is probably easiest. I was just keen to see the "major bugfixes" get into 22, rather than waiting another few months for 23. cheers -- Michael Ellerman OzLabs, IBM Australia Development Lab wwweb: http://michael.ellerman.id.au phone: +61 2 6212 1183 (tie line 70 21183) We do not inherit the earth from our ancestors, we borrow it from our children. - S.M.A.R.T Person
signature.asc
Description: This is a digitally signed message part
