linux-kernel - Diagnosing linux-next (Was: Re: m68k libc5 regression)

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]

Date:	Sun, 1 Jun 2008 23:26:38 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Linux Kernel Development <linux-kernel@...r.kernel.org>,
	linux-next@...r.kernel.org
Subject: Diagnosing linux-next (Was: Re: m68k libc5 regression)

Hi Andrew,

On Sun, 1 Jun 2008 00:53:38 -0700 Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> I do not know how to work out how this patch got into linux-next.

I have been wondering for a while what I can do to make figuring this out
(in general) easier.  Would adding the SHA1 of the head of each tree to
the Trees file help?  I could publish all the branches in my linux-next
repo - but they change daily.  I guess only the git users benefit from
those suggestions.

gitk can tell you pretty easily (just find the offending commit and work
your way upward until you find a merge by me).

Other suggestions?
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped