[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0708091721030.24369@kivilampi-30.cs.helsinki.fi>
Date: Thu, 9 Aug 2007 17:40:07 +0300 (EEST)
From: "Ilpo Järvinen" <ilpo.jarvinen@...sinki.fi>
To: David Miller <davem@...emloft.net>
cc: Netdev <netdev@...r.kernel.org>
Subject: Re: net-2.6.24 GIT state
On Thu, 9 Aug 2007, David Miller wrote:
> From: "Ilpo_Järvinen" <ilpo.jarvinen@...sinki.fi>
> Date: Thu, 9 Aug 2007 12:50:51 +0300 (EEST)
>
> Ok, in order to get this started I merged the above patches
> into net-2.6.24
>
> I'm exhausted and done for today. :-)
:-)
> We can work on the other bits next.
Next step:
http://www.cs.helsinki.fi/u/ijjarvin/tcp-rebase/after-reorder/
...I put some effort to reorganization and there's the result, please
_don't_ take the new SACK block-validator yet as I haven't yet put it
under any testing (it's the only difference this reordering of patches
seems to have introduced :-)). The first five commits touch left_out (4
latest fix bug and "flaws" I made in the first commit), I could combine
them into a single one if you want to.
...Notice that part of the next step includes work that hasn't yet been
posted to netdev at all (was from my not yet submitted wip portion of
it). Would you prefer me to post them using the usual procedure?
> > ...Taking IsReno/IsFack removal is probably going to be hardest one, as it
> > will conflict a lot. ...Maybe some sed work in patches would reduce # of
> > conflicts instead of trying cherry-pick+rebase.
>
> Yes, such patch hand editing techniques can help in these cases.
...it helped a lot in the process :-).
--
i.
Powered by blists - more mailing lists