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.
To move forward, it sounds like the best thing to do is drop all
spidernet patches and start over, yes?
Jeff
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
