From: Andy Whitcroft <apw@shadowen.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Feb 15
Date: Fri, 15 Feb 2008 10:01:09 +0000 [thread overview]
Message-ID: <20080215100109.GD24479@shadowen.org> (raw)
In-Reply-To: <20080215183143.c811803c.sfr@canb.auug.org.au>
On Fri, Feb 15, 2008 at 06:31:43PM +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.
>
> Between each merge, the tree was built with allmodconfig for both
> powerpc and x86_64.
>
> You can see which trees have been included by looking in the Trees file
> in the source.
>
> 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.
Thats cool except that the tags seem to be missing in your public tree.
Tags do not get pushed automatically, you have to push them manually,
perhaps they were missed?
> There were a couple of merge conflicts and one build failure and the
> appropriate people contacted.
>
> We are up to 18 trees, more are welcome.
-apw
next prev parent reply other threads:[~2008-02-15 10:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 7:31 linux-next: Tree for Feb 15 Stephen Rothwell
2008-02-15 10:01 ` Andy Whitcroft [this message]
2008-02-15 11:09 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2012-02-15 5:03 Stephen Rothwell
2013-02-15 7:42 Stephen Rothwell
2013-02-15 7:42 ` Stephen Rothwell
2013-02-15 9:24 ` Arend van Spriel
2013-02-15 10:58 ` Sedat Dilek
2016-02-15 5:40 Stephen Rothwell
2017-02-15 5:49 Stephen Rothwell
2018-02-15 3:35 Stephen Rothwell
2019-02-15 6:03 Stephen Rothwell
2021-02-15 9:34 Stephen Rothwell
2022-02-15 9:13 Stephen Rothwell
2023-02-15 3:50 Stephen Rothwell
2024-02-15 3:52 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=20080215100109.GD24479@shadowen.org \
--to=apw@shadowen.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.