[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080423010458.4114ec83.sfr@canb.auug.org.au>
Date: Wed, 23 Apr 2008 01:04:58 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Russell King <rmk+lkml@....linux.org.uk>
Cc: linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Linus' tree build breakage
Hi Russell,
On Tue, 22 Apr 2008 08:36:22 +0100 Russell King <rmk+lkml@....linux.org.uk> wrote:
>
> linux-next will not give me anything which -mm isn't giving me. As I
> said in the discussion, linux-next value is _very_ small for me.
Let me try again (others may want to read as well).
What you get:
- 5 times a week your tree gets merged with lots of other code
destined for Linus' next release. From this you get to find
out about things in other trees that clash with yours.
- This tree gets built on several architectures for several configs
(including arm). So you find out if other trees will break yours.
- I am happy to build more (basically all) the arm configs as I
have offered before.
What others get:
- You get told if your changes clash or break other's changes.
- They get told if your tree may require changes to theirs.
What it costs:
- you need to create a tree (o quilt series) that contains the
changes you expect to submit to Linus in the next merge window.
This is not so different from the tree you currently send to
Andrew (and is probably a subset of that). You update this tree
as you want to and I fetch it at least daily.
- Reading a few extra emails if/when I find problems that may
concern you.
Thanks for listening.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists