linux-kernel - Re: Announce: Linux-next (Or Andrew's dream :-))

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: <1203258465.3082.13.camel@localhost.localdomain>
Date:	Sun, 17 Feb 2008 08:27:45 -0600
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Roland Dreier <rdreier@...co.com>,
	LKML <linux-kernel@...r.kernel.org>, linux-next@...r.kernel.org,
	linux-arch@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus <torvalds@...ux-foundation.org>
Subject: Re: Announce: Linux-next (Or Andrew's dream  :-))

On Sun, 2008-02-17 at 16:25 +1100, Stephen Rothwell wrote:
> Hi James,
> 
> On Sat, 16 Feb 2008 09:14:32 -0600 James Bottomley <James.Bottomley@...senPartnership.com> wrote:
> >
> > Do you have the tree and build logs available anywhere?  I'd like to
> > turn off the merge tree builds when this is able to replace it.
> 
> The tree is at
> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git - or did
> you mean the logs of creating the tree.

Yes, the logs of creating the tree.

>   I currently ceate the tree
> fairly manually (as I slowly script what can be) and so have no logs of
> that process.

Um, well, I've already pointed to tools that currently do this bit
automatically.  Do you have a list of input trees anywhere?

> The build logs that I have some control over are at
> http://kisskb.ellerman.id.au/kisskb/branch/9/.  I am hoping to expand on
> the arch/config combinations over time (I have to convince my tame cross
> compiler builder :-)).  I also hope that others will build this tree for
> themselves and publish the results.

Oh, OK ... by build I mean combine the trees and quilts into the actual
tree.  Compiling is nice, but it's the tree construction logs I want to
see to make sure there aren't any impending merge problems.  Most people
verify on a fairly constant basis that their own trees actually build.
The only problems we have are edge configurations (like arm and sparc,
which have SCSI drivers that don't build except on those architectures).

James


--
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/