From: Jeff Garzik <jgarzik@pobox.com>
To: "Hen, Shmulik" <shmulik.hen@intel.com>
Cc: bonding-devel@lists.sourceforge.net, netdev@oss.sgi.com
Subject: Re: [bonding][2/3] Synchronizing 2.4-2.6
Date: Thu, 28 Aug 2003 12:02:42 -0400 [thread overview]
Message-ID: <3F4E27A2.9060204@pobox.com> (raw)
In-Reply-To: <E791C176A6139242A988ABA8B3D9B38A014C94E5@hasmsx403.iil.intel.com>
Hen, Shmulik wrote:
>>-----Original Message-----
>>From: Jeff Garzik [mailto:jgarzik@pobox.com]
>>Sent: Thursday, August 28, 2003 12:52 AM
>>To: Hen, Shmulik
>>Cc: bonding-devel@lists.sourceforge.net; netdev@oss.sgi.com
>>Subject: Re: [bonding][2/3] Synchronizing 2.4-2.6
>>
>>
>>Shmulik Hen wrote:
>>
>>>This is set 2 that merges parts of Jay Vosburgh's experimental
>>>propagation stuff from 5/22 with all the fixes/enhancements
>>>we've developed according to the RFC published on bond-devel
>>>list on 6/2.
>>>
>>>Applies on 2.4.22. Assumes patch set 1 was already applied.
>>
>>
>>As Jay mentioned he had approved through the end of set 2, and set 2
>>looks good to me, I applied all 8 patches to 2.4.
>>
>
>
> Does that mean patch set 2 was also applied ?
Yes.
>>Let's now take an operational pause in 2.4, and get 2.6 back
>>into sync.
>> Would some hearty bonding team member(s) be willing to do that?
>>
>
>
> After patch set 1, It should be as easy as just copying all the
> bonding related files from 2.4 to 2.6. I guess I can do that on
> Sunday if someone hasn't already done it before.
I had hoped to preserve the revision history. Simply copying the files
over does not do that :(
What I mean by preserving revision history is, changes should be
submitted to 2.6 in the same granularity as they were to 2.4...
Jeff
next prev parent reply other threads:[~2003-08-28 16:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 7:26 [bonding][2/3] Synchronizing 2.4-2.6 Hen, Shmulik
2003-08-28 16:02 ` Jeff Garzik [this message]
2003-08-30 19:39 ` [Bonding-devel] " Shmulik Hen
2003-08-30 19:55 ` Ben Greear
2003-08-30 21:26 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2003-08-31 12:19 Hen, Shmulik
2003-08-27 17:03 Shmulik Hen
2003-08-27 21:51 ` 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=3F4E27A2.9060204@pobox.com \
--to=jgarzik@pobox.com \
--cc=bonding-devel@lists.sourceforge.net \
--cc=netdev@oss.sgi.com \
--cc=shmulik.hen@intel.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).