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 18
Date: Mon, 18 Feb 2008 19:08:41 +1100 [thread overview]
Message-ID: <20080218190841.eeed735f.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 789 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.
The tree is now tagged with a tag like next-YYYYMMDD and has a
localversion-next file which adds "-next-YYYYMMDD" to the kernel revision.
There were a couple of merge conflicts and a couple of build failures and
the appropriate people contacted.
We are up to 24 trees, more are welcome.
--
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-18 8:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 8:08 Stephen Rothwell [this message]
2008-02-18 8:14 ` Avi Kivity
2008-02-18 8:34 ` Stephen Rothwell
2008-02-18 8:47 ` David Miller
2008-02-18 23:56 ` Bartlomiej Zolnierkiewicz
2013-02-18 6:16 Stephen Rothwell
2014-02-18 5:06 Stephen Rothwell
2015-02-18 3:22 Stephen Rothwell
2016-02-18 7:31 Stephen Rothwell
2019-02-18 7:36 Stephen Rothwell
2020-02-18 4:28 Stephen Rothwell
2021-02-18 9:54 Stephen Rothwell
2025-02-18 5:15 Stephen Rothwell
2026-02-18 13:24 Mark Brown
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=20080218190841.eeed735f.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome