From: Stephen Rothwell <sfr@canb.auug.org.au>
To: linux-next@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: linux-next: Tree for Feb 19
Date: Tue, 19 Feb 2008 18:38:25 +1100 [thread overview]
Message-ID: <20080219183825.1c71c9b2.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
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.
There were a couple of merge conflicts and a couple of build failures and
the appropriate people contacted.
We are up to 26 trees, more are welcome (even if they are currently empty).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2008-02-19 7:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 7:38 Stephen Rothwell [this message]
2008-02-19 20:04 ` linux-next: Tree for Feb 19 David Teigland
2008-02-19 23:03 ` Stephen Rothwell
2008-02-19 23:08 ` David Teigland
2013-02-19 6:03 Stephen Rothwell
2013-02-19 6:03 ` Stephen Rothwell
2014-02-19 5:47 Stephen Rothwell
2014-02-19 5:47 ` Stephen Rothwell
2015-02-19 5:03 Stephen Rothwell
2016-02-19 4:49 Stephen Rothwell
2018-02-19 2:14 Stephen Rothwell
2018-02-19 17:26 ` Randy Dunlap
2019-02-19 8:30 Stephen Rothwell
2020-02-19 2:50 Stephen Rothwell
2021-02-19 10:08 Stephen Rothwell
2024-02-19 5:25 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=20080219183825.1c71c9b2.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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.