All of lore.kernel.org
 help / color / mirror / Atom feed
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
Date: Tue, 19 Feb 2008 21:50:55 -0800	[thread overview]
Message-ID: <20080220055055.GC31832@kroah.com> (raw)
In-Reply-To: <20080220163457.79b9189f.sfr@canb.auug.org.au>

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

  reply	other threads:[~2008-02-20  5:53 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20  5:34 linux-next: Tree for Feb 20 Stephen Rothwell
2008-02-20  5:50 ` Greg KH [this message]
2008-02-20  5:55   ` David Miller
2008-02-20  6:16   ` Chris Wedgwood
2008-02-20  6:57   ` Stephen Rothwell
2008-02-20  7:49     ` Frank Seidel
2008-02-20  7:46   ` Jeff Garzik
2008-02-20  8:13 ` Adrian Bunk
2008-02-20 14:59 ` James Bottomley
2008-02-20 15:20   ` Stephen Rothwell
2008-02-20 15:56     ` James Bottomley
2008-02-20 15:24   ` Frank Seidel
2012-02-20  5:59 Stephen Rothwell
2013-02-20  6:50 Stephen Rothwell
2013-02-20  6:50 ` Stephen Rothwell
2014-02-20  6:58 Stephen Rothwell
2014-02-20  6:58 ` Stephen Rothwell
2015-02-20  1:59 Stephen Rothwell
2017-02-20  4:57 Stephen Rothwell
2018-02-20  2:44 Stephen Rothwell
2019-02-20  7:43 Stephen Rothwell
2019-02-20  9:11 ` Zhangshaokun
2019-02-20  9:52   ` Jarkko Sakkinen
2019-02-20  9:58     ` Jarkko Sakkinen
2019-02-20 10:05       ` Ard Biesheuvel
2019-02-20 12:17         ` Mimi Zohar
2019-02-21  0:43         ` Zhangshaokun
2019-02-21  8:03           ` Geert Uytterhoeven
2019-02-21  8:42             ` Zhangshaokun
2019-02-21  9:12             ` Ard Biesheuvel
2020-02-20  3:44 Stephen Rothwell
2023-02-20  5:39 Stephen Rothwell
2024-02-20  5:13 Stephen Rothwell

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=20080220055055.GC31832@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.