2003-03-20 22:45:27

by Jay Vosburgh

[permalink] [raw]
Subject: Re: [Bonding-devel] [patch] (2/8) Add 802.3ad support to bonding (released to bonding on sourceforge)






I have incorporated Shmulik Hen's bug fix patches to bonding (patch
numbers 2 and 3) into the current code and released the new patch to
sourceforge.net/projects/bonding. The current bonding update is
bonding-2.4.20-20030320. The only changes I made were minor spelling /
formatting fixes.

-J



2003-03-20 23:59:42

by David Miller

[permalink] [raw]
Subject: Re: [Bonding-devel] [patch] (2/8) Add 802.3ad support to bonding (released to bonding on sourceforge)

From: Jay Vosburgh <[email protected]>
Date: Thu, 20 Mar 2003 14:53:14 -0800

I have incorporated Shmulik Hen's bug fix patches to bonding (patch
numbers 2 and 3) into the current code and released the new patch to
sourceforge.net/projects/bonding. The current bonding update is
bonding-2.4.20-20030320. The only changes I made were minor spelling /
formatting fixes.

So when do these changes end up being sent to myself or
Jeff for mainline inclusion?

I have no objection to the sourceforge project for bonding, but
I do object to there being such latency between what the sourceforge
tree has (especially bug fixes) and what gets submitted into the
mainline.

Personally, I'd prefer that all development occur in the mainline
tree. That gives you testing coverage that is impossible otherwise.