Date: Tue, 19 Feb 2008 21:50:55 -0800
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
       linux-arch@vger.kernel.org
Subject: Re: linux-next: Tree for Feb 20
Message-ID: <20080220055055.GC31832@kroah.com>
References: <20080220163457.79b9189f.sfr@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080220163457.79b9189f.sfr@canb.auug.org.au>
User-Agent: Mutt/1.5.16 (2007-06-09)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1774
Lines: 44

On Wed, Feb 20, 2008 at 04:34:57PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
> 
> You can see which trees have been included by looking in the Next/Trees
> file in the source.  There are also quilt-import.log and merge.log files
> in the Next directory.  Between each merge, the tree was built with
> allmodconfig for both powerpc and x86_64.

What's the best way to constantly follow this tree?  I had cloned it a
while ago, but now if I 'git pull' it wants to merge things, which isn't
right.

I'm guessing that this is constantly being rebased?  Against what,
Linus's tree?  So we should be able to clone Linus's tree, and then pull
in -next?

Or am I totally missing something here?

> There were no merge conflicts and only one build failure!
> 
> We are up to 27 trees, more are welcome (even if they are currently
> empty).  I would encourage architecture maintainers, in particular, to
> set up a git branch or quilt tree now to avoid the rush after RC2 :-)
> 
> I will stop making these announcements now unless there is some change to
> the tree or things people should know.  There should be a new tree every
> (Australian Capital Territory) working day.

I like seeing these, to know that things are at least still working.  I
imagine you could script them, or just send them to the linux-next list
if there are no problems, but lkml should probably be notified of any
issues, right?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/