From: James Bottomley <James.Bottomley@HansenPartnership.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: Wed, 20 Feb 2008 09:56:17 -0600 [thread overview]
Message-ID: <1203522977.3109.20.camel@localhost.localdomain> (raw)
In-Reply-To: <20080221022057.c0da8d05.sfr@canb.auug.org.au>
On Thu, 2008-02-21 at 02:20 +1100, Stephen Rothwell wrote:
> Hi James,
>
> On Wed, 20 Feb 2008 08:59:20 -0600 James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> >
> > Is the merge log available anywhere yet?
>
> Are you looking for more that what is in Next/merge.log in the tree?
Yes, that's it, thanks!
James
next prev parent reply other threads:[~2008-02-20 15:56 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
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 [this message]
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=1203522977.3109.20.camel@localhost.localdomain \
--to=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 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.