linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Seidel <fseidel@suse.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	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: Wed, 20 Feb 2008 16:24:57 +0100	[thread overview]
Message-ID: <47BC4649.6060304@suse.de> (raw)
In-Reply-To: <1203519560.3109.6.camel@localhost.localdomain>

James Bottomley wrote:
> On Wed, 2008-02-20 at 16:34 +1100, Stephen Rothwell wrote:
>> There were no merge conflicts and only one build failure!
> 
> Is the merge log available anywhere yet?

Yes, there is the Next/merge.log file in linux-next.
http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git;a=blob;f=Next/merge.log;hb=HEAD

This is also now documented on the pages i setup on
http://linux.f-seidel.de/linux-next/
while this
http://linux.f-seidel.de/linux-next/pmwiki/pmwiki.php?n=Linux-next.ShortSummary
holds most of it in a short form.

Thanks,
Frank

      parent reply	other threads:[~2008-02-20 15:25 UTC|newest]

Thread overview: 12+ 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
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 [this message]

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=47BC4649.6060304@suse.de \
    --to=fseidel@suse.de \
    --cc=James.Bottomley@HansenPartnership.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).