linux-kernel - Re: linux-next: Tree for Feb 15

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080215100109.GD24479@shadowen.org>
Date:	Fri, 15 Feb 2008 10:01:09 +0000
From:	Andy Whitcroft <apw@...dowen.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for Feb 15

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/