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

[Stephen Boyd]

On 8/2/2011 9:42 PM, 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
>

Could you use git get-tar-commit-id?

$ git get-tar-commit-id < linux-3.0.tar

It won't work for the patch ones though.

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/