From: Stephen Boyd <sboyd@codeaurora.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: git commit id and tarball's filename mapping.
Date: Wed, 03 Aug 2011 01:32:05 -0700 [thread overview]
Message-ID: <4E390785.4060007@codeaurora.org> (raw)
In-Reply-To: <201108030442.p734gwO9050751@www262.sakura.ne.jp>
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.
prev parent reply other threads:[~2011-08-03 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E390785.4060007@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox