[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <11481.1209670599@turing-police.cc.vt.edu>
Date: Thu, 01 May 2008 15:36:39 -0400
From: Valdis.Kletnieks@...edu
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: Willy Tarreau <w@....eu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
David Miller <davem@...emloft.net>,
linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Jiri Slaby <jirislaby@...il.com>
Subject: Re: Slow DOWN, please!!!
On Thu, 01 May 2008 13:53:18 +0200, "Rafael J. Wysocki" said:
> How about:
>
> (1) Merge a couple of trees at a time (one tree at a time would be ideal, but
> that's impossible due to the total number of trees).
> (2) After (1) give testers some time to report problems introduced by the
> merge.
> (3) Wait until the most urgent problems are resolved. Revert the offending
> changes if there's no solution within given time.
> (4) Repeat for another couple of trees.
> (5) Arrange things so that every tree gets merged once every two months.
You can't get there from here (at least not very easily).
If you have 60 trees, and want a merge for each one every 2 months, you have to
average 1 tree a day. How big a delay you want in step (2) directly impacts
how many trees you merge at once - if you want a week of cook time, you have to
merge 7 trees every Monday, and so on...
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists