linux-kernel - Re: git commit id and tarball's filename mapping.

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: <201108030502.p7352IDa055880@www262.sakura.ne.jp>
Date:	Wed, 03 Aug 2011 14:02:18 +0900
From:	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To:	davej@...hat.com
Cc:	linux-kernel@...r.kernel.org
Subject: Re: git commit id and tarball's filename mapping.

Dave Jones wrote:
> On Wed, Aug 03, 2011 at 01:42:58PM +0900, Tetsuo Handa wrote:
>  > I regularly test kernels extracted from tarballs rather than from git. I have
>  > problems with estimating range to "git bisect" because I can't know commit id
>  > as of a tarball was archived. I would appreciate if there is a mapping table
>  > that contains commit id and tarball's filename.
> 
> for the patches, there's an associated .id file in the same dir.
Oh, that's good.

> Seems to be lacking for the tarballs though.
We can use alias names assigned by "git tag".

Thank you.
--
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/