* git commit id and tarball's filename mapping.
@ 2011-08-03 4:42 Tetsuo Handa
2011-08-03 4:47 ` Dave Jones
2011-08-03 8:32 ` Stephen Boyd
0 siblings, 2 replies; 4+ messages in thread
From: Tetsuo Handa @ 2011-08-03 4:42 UTC (permalink / raw)
To: linux-kernel
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: git commit id and tarball's filename mapping.
2011-08-03 4:42 git commit id and tarball's filename mapping Tetsuo Handa
@ 2011-08-03 4:47 ` Dave Jones
2011-08-03 5:02 ` Tetsuo Handa
2011-08-03 8:32 ` Stephen Boyd
1 sibling, 1 reply; 4+ messages in thread
From: Dave Jones @ 2011-08-03 4:47 UTC (permalink / raw)
To: Tetsuo Handa; +Cc: linux-kernel
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: git commit id and tarball's filename mapping.
2011-08-03 4:47 ` Dave Jones
@ 2011-08-03 5:02 ` Tetsuo Handa
0 siblings, 0 replies; 4+ messages in thread
From: Tetsuo Handa @ 2011-08-03 5:02 UTC (permalink / raw)
To: davej; +Cc: linux-kernel
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: git commit id and tarball's filename mapping.
2011-08-03 4:42 git commit id and tarball's filename mapping Tetsuo Handa
2011-08-03 4:47 ` Dave Jones
@ 2011-08-03 8:32 ` Stephen Boyd
1 sibling, 0 replies; 4+ messages in thread
From: Stephen Boyd @ 2011-08-03 8:32 UTC (permalink / raw)
To: Tetsuo Handa; +Cc: linux-kernel
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-08-03 8:32 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-08-03 4:42 git commit id and tarball's filename mapping Tetsuo Handa
2011-08-03 4:47 ` Dave Jones
2011-08-03 5:02 ` Tetsuo Handa
2011-08-03 8:32 ` Stephen Boyd
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox