From: Pascal Obry <pascal@obry.net>
To: git list <git@vger.kernel.org>
Subject: Git tree/blob and corresponding commit
Date: Sun, 10 Aug 2008 19:08:27 +0200 [thread overview]
Message-ID: <489F208B.2070006@obry.net> (raw)
Something I'm trying to figure out and can't find the answer myself. I'm
browsing a tree, for example:
$ git ls-tree HEAD~100
This list a set of files with the corresponding blob. Each blob has it's
own SHA1. Fine.
Now given a SHA1 I'd like to know which commit has created (was
containing) this specific blob?
What is the best way to achieve that?
Thanks.
--
--|------------------------------------------------------
--| Pascal Obry Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--| http://www.obry.net
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595
next reply other threads:[~2008-08-10 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-10 17:08 Pascal Obry [this message]
2008-08-10 20:38 ` Git tree/blob and corresponding commit Jonathan Nieder
2008-08-10 20:44 ` Jonathan Nieder
2008-08-14 14:02 ` Pascal Obry
2008-08-15 19:39 ` Bryan Donlan
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=489F208B.2070006@obry.net \
--to=pascal@obry.net \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).