linux-kernel - Re: git trees which are not yet in linux-next

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: <20080502154200.a6d8c43a.akpm@linux-foundation.org>
Date:	Fri, 2 May 2008 15:42:00 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	linux-next@...r.kernel.org, sfrench@...ibm.com,
	swhiteho@...hat.com, stefanr@...6.in-berlin.de, jeff@...zik.org,
	ralf@...ux-mips.org, drzeus-list@...eus.cx, jack@....cz,
	cbou@...l.ru, jens.axboe@...cle.com, ericvh@...il.com,
	wim@...ana.be, chris@...kel.net, nico@....org,
	penberg@...helsinki.fi, clameter@....com, ezk@...sunysb.edu,
	linux-kernel@...r.kernel.org
Subject: Re: git trees which are not yet in linux-next

On Fri, 2 May 2008 15:12:06 -0700
Andrew Morton <akpm@...ux-foundation.org> wrote:

> The first
> problem is working out "how the heck did that patch get into linux-next"? 
> That would be much easier if the signoff trail was complete for git-based
> patches, but it often is not.

doh.  I'm pulling linux-next's constituent trees independently, so if I
spot a turd in linux-next I can just grep the various git trees to find out
where it came from.

It seems wrong though...
--
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/