From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Linus' tree build breakage
Date: Wed, 23 Apr 2008 01:04:58 +1000 [thread overview]
Message-ID: <20080423010458.4114ec83.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080422073622.GB22955@flint.arm.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1395 bytes --]
Hi Russell,
On Tue, 22 Apr 2008 08:36:22 +0100 Russell King <rmk+lkml@arm.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@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-04-22 15:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 0:31 Stephen Rothwell
2008-04-22 7:36 ` Russell King
2008-04-22 7:43 ` David Miller
2008-04-22 13:58 ` Andrew Morton
2008-04-22 15:04 ` Stephen Rothwell [this message]
2008-04-22 22:30 ` Greg KH
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=20080423010458.4114ec83.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®