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

[Dave Jones <davej@redhat.com>]

On Wed, Aug 03, 2011 at 01:42:58PM +0900, Tetsuo Handa wrote:
 > Hello.
 > 
 > 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.
 > 
 > 0123456789012345678901234567890123456789 linux-3.0.tar.bz2
 > 1234567890123456789012345678901234567890 patch-3.0-git1.bz2
 > 2345678901234567890123456789012345678901 patch-3.0-git2.bz2
 > 3456789012345678901234567890123456789012 patch-3.0-git3.bz2
 >   (...snipped...)
 > 7890123456789012345678901234567890123456 patch-3.0-git17.bz2
 > 8901234567890123456789012345678901234567 linux-3.1-rc1.tar.bz2

for the patches, there's an associated .id file in the same dir.
Seems to be lacking for the tarballs though.

	Dave