From: "David S. Miller" <davem@redhat.com>
To: fubar@us.ibm.com
Cc: hshmulik@intel.com, bonding-devel@lists.sourceforge.net,
bonding-announce@lists.sourceforge.net,
linux-net@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@oss.sgi.com, jgarzik@pobox.com
Subject: Re: [Bonding-devel] [patch] (2/8) Add 802.3ad support to bonding (released to bonding on sourceforge)
Date: Thu, 20 Mar 2003 16:08:45 -0800 (PST) [thread overview]
Message-ID: <20030320.160845.121240938.davem@redhat.com> (raw)
In-Reply-To: <OF102C4F31.A103F2FF-ON88256CEF.007C2E59@us.ibm.com>
From: Jay Vosburgh <fubar@us.ibm.com>
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.
next prev parent reply other threads:[~2003-03-21 0:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 22:53 [Bonding-devel] [patch] (2/8) Add 802.3ad support to bonding (released to bonding on sourceforge) Jay Vosburgh
2003-03-21 0:08 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-21 0:43 Jay Vosburgh
2003-03-21 0:57 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030320.160845.121240938.davem@redhat.com \
--to=davem@redhat.com \
--cc=bonding-announce@lists.sourceforge.net \
--cc=bonding-devel@lists.sourceforge.net \
--cc=fubar@us.ibm.com \
--cc=hshmulik@intel.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).