From: Jeff Garzik <jgarzik@pobox.com>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: "David S. Miller" <davem@redhat.com>,
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
Subject: Re: [Bonding-devel] [patch] (2/8) Add 802.3ad support to bonding (released to bonding on sourceforge)
Date: Thu, 20 Mar 2003 19:57:00 -0500 [thread overview]
Message-ID: <3E7A635C.3090000@pobox.com> (raw)
In-Reply-To: <OF1BD71312.6E4C42DC-ON88256CF0.000314A8@us.ibm.com>
Jay Vosburgh wrote:
> Fair enough; the delay has gotten excessive of late.
>
> Would it be satisfactory going forward for the sourceforge site to
> contain patches to "standard" releases (e.g., 2.4.20), and do updates to
> the current development kernel and the sourceforge site simultaneously? In
> other words, sourceforge has a patch containing all bonding updates since
> 2.4.20 (or whichever version) was released, and each time that patch is
> updated, the incremental update goes out for inclusion in the development
> kernel.
The ideal situation is for you to send two sets of patches, one for 2.4
tree and one for 2.5 tree. Those will get applied to 2.4.21-pre and
2.5.<latest>. Patches against 2.4.20 proper are ok as long as they
apply correctly to the latest 2.4.21-pre tree (so, patches against
2.4.21-pre are preferred)
If the patches are the same for 2.4 and 2.5, just send one set and note
that fact. My preference would be to address these patches
To: davem@redhat.com
CC: netdev@oss.sgi.com, jgarzik@pobox.com
(David, feel free to correct me here, or direct patches to me)
When you receive bug fixes, forwarding ASAP would be very much appreciated.
Jeff
next prev parent reply other threads:[~2003-03-21 0:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-21 0:43 [Bonding-devel] [patch] (2/8) Add 802.3ad support to bonding (released to bonding on sourceforge) Jay Vosburgh
2003-03-21 0:57 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-20 22:53 Jay Vosburgh
2003-03-21 0:08 ` David S. Miller
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=3E7A635C.3090000@pobox.com \
--to=jgarzik@pobox.com \
--cc=bonding-announce@lists.sourceforge.net \
--cc=bonding-devel@lists.sourceforge.net \
--cc=davem@redhat.com \
--cc=fubar@us.ibm.com \
--cc=hshmulik@intel.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).