[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080214081405.GA20791@flint.arm.linux.org.uk>
Date: Thu, 14 Feb 2008 08:14:05 +0000
From: Russell King <rmk+lkml@....linux.org.uk>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Theodore Tso <tytso@....edu>,
Trond Myklebust <trond.myklebust@....uio.no>,
Arjan van de Ven <arjan@...radead.org>,
Greg KH <greg@...ah.com>, LKML <linux-kernel@...r.kernel.org>,
linux-next@...r.kernel.org, linux-arch@...r.kernel.org,
Linus <torvalds@...ux-foundation.org>
Subject: Re: Announce: Linux-next (Or Andrew's dream :-))
On Tue, Feb 12, 2008 at 10:57:16PM +1100, Stephen Rothwell wrote:
> We need to ask Linus to promise that he will pull the stable branch from
> linux-next first in the merge window. For that to happen, I would expect
> that Linus would also review and sign off (or ack) these commits to the
> linux-next tree.
Changing the commits in git in anyway changes their ID, which has the
same effects as a rebase.
With this idea, Linus only has two choices:
1. pull the entire set of linux-next changes whether he likes them or not,
because he's going to get them either from the linux-next tree or someone
elses tree which is based upon that.
2. don't pull the changes, nor anyone elses tree if he hates the changes
in linux-next.
So really, Linus needs to ack the changes _before_ they go into linux-next.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists