* RE: [bonding][2/3] Synchronizing 2.4-2.6
@ 2003-08-28 7:26 Hen, Shmulik
2003-08-28 16:02 ` Jeff Garzik
0 siblings, 1 reply; 5+ messages in thread
From: Hen, Shmulik @ 2003-08-28 7:26 UTC (permalink / raw)
To: Jeff Garzik; +Cc: bonding-devel, netdev
> -----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 ?
Because that was the first thing to do to get versions synched.
> 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 would _really_ prefer that the revision history be
> maintained, which
> makes it a non-trivial exercise, time-wise...
Where should that be maintained ?
I could suggest the CVS on SFG.
Shmulik.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [bonding][2/3] Synchronizing 2.4-2.6
2003-08-28 7:26 [bonding][2/3] Synchronizing 2.4-2.6 Hen, Shmulik
@ 2003-08-28 16:02 ` Jeff Garzik
2003-08-30 19:39 ` [Bonding-devel] " Shmulik Hen
0 siblings, 1 reply; 5+ messages in thread
From: Jeff Garzik @ 2003-08-28 16:02 UTC (permalink / raw)
To: Hen, Shmulik; +Cc: bonding-devel, netdev
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Bonding-devel] Re: [bonding][2/3] Synchronizing 2.4-2.6
2003-08-28 16:02 ` Jeff Garzik
@ 2003-08-30 19:39 ` Shmulik Hen
2003-08-30 19:55 ` Ben Greear
2003-08-30 21:26 ` Jeff Garzik
0 siblings, 2 replies; 5+ messages in thread
From: Shmulik Hen @ 2003-08-30 19:39 UTC (permalink / raw)
To: Jeff Garzik; +Cc: bonding-devel, netdev
On Thursday 28 August 2003 07:02 pm, Jeff Garzik wrote:
> Hen, Shmulik wrote:
> > 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...
>
God, I wish I was an English speaking person... :(
Amir, on the other hand, understood exactly what you intended, so
there should be something ready for tomorrow that brings 2.6 to the
same point as 2.4 after set 1, in small steps. After that, sets 2 and
3 could be applied the same way for 2.4 and 2.6.
Shmulik.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Bonding-devel] Re: [bonding][2/3] Synchronizing 2.4-2.6
2003-08-30 19:39 ` [Bonding-devel] " Shmulik Hen
@ 2003-08-30 19:55 ` Ben Greear
2003-08-30 21:26 ` Jeff Garzik
1 sibling, 0 replies; 5+ messages in thread
From: Ben Greear @ 2003-08-30 19:55 UTC (permalink / raw)
To: shmulik.hen; +Cc: Jeff Garzik, bonding-devel, netdev
Shmulik Hen wrote:
> On Thursday 28 August 2003 07:02 pm, Jeff Garzik wrote:
>
>>Hen, Shmulik wrote:
>>
>>>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...
>>
>
>
> God, I wish I was an English speaking person... :(
Don't feel bad, I had no clue what he was asking for
either :)
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Bonding-devel] Re: [bonding][2/3] Synchronizing 2.4-2.6
2003-08-30 19:39 ` [Bonding-devel] " Shmulik Hen
2003-08-30 19:55 ` Ben Greear
@ 2003-08-30 21:26 ` Jeff Garzik
1 sibling, 0 replies; 5+ messages in thread
From: Jeff Garzik @ 2003-08-30 21:26 UTC (permalink / raw)
To: shmulik.hen; +Cc: bonding-devel, netdev
Shmulik Hen wrote:
> On Thursday 28 August 2003 07:02 pm, Jeff Garzik wrote:
>
>>Hen, Shmulik wrote:
>>
>>>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...
>>
>
>
> God, I wish I was an English speaking person... :(
> Amir, on the other hand, understood exactly what you intended, so
> there should be something ready for tomorrow that brings 2.6 to the
> same point as 2.4 after set 1, in small steps. After that, sets 2 and
> 3 could be applied the same way for 2.4 and 2.6.
No worries. Even I don't understand myself sometimes. :)
Jeff
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2003-08-30 21:26 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-08-28 7:26 [bonding][2/3] Synchronizing 2.4-2.6 Hen, Shmulik
2003-08-28 16:02 ` Jeff Garzik
2003-08-30 19:39 ` [Bonding-devel] " Shmulik Hen
2003-08-30 19:55 ` Ben Greear
2003-08-30 21:26 ` Jeff Garzik
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).