From: Alex Riesen <raa.lkml@gmail.com>
To: Eugene Sajine <euguess@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: ident hash usage question
Date: Tue, 20 Oct 2009 20:19:30 +0200 [thread overview]
Message-ID: <81b0412b0910201119w7583487ag276cf964d0a85e@mail.gmail.com> (raw)
In-Reply-To: <81b0412b0910201116s694d7877rda872b368f1ae09a@mail.gmail.com>
On Tue, Oct 20, 2009 at 20:16, Alex Riesen <raa.lkml@gmail.com> wrote:
> On Tue, Oct 20, 2009 at 19:24, Eugene Sajine <euguess@gmail.com> wrote:
>> I was able to get the $Id$ keyword to show the SHA-1 hash of the file
>> content, which is done using ident in gitattributes. Now I’m trying to
>> find a way to get more info about the file using only this hash.
>>
>> Could you , please, advise if there is a way to get file name and path
>> inside the repo by having only this Blob hash?
>
> It is not possible.
>
Well, not exactly impossible, but you can end up with multiple paths,
some of which may not have anything to do the original path.
Just run git log --no-abbrev --raw --all and grep for the SHA-1
next prev parent reply other threads:[~2009-10-20 18:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 17:24 ident hash usage question Eugene Sajine
2009-10-20 18:16 ` Alex Riesen
2009-10-20 18:19 ` Alex Riesen [this message]
2009-10-20 18:59 ` Eugene Sajine
2009-10-20 19:19 ` Alex Riesen
2009-10-20 20:22 ` Johannes Sixt
2009-10-20 20:35 ` Alex Riesen
2009-10-20 20:30 ` Eugene Sajine
2009-10-20 20:43 ` Junio C Hamano
2009-10-20 22:14 ` Eugene Sajine
2009-10-20 22:30 ` Junio C Hamano
2009-10-20 23:49 ` Eugene Sajine
2009-10-21 5:35 ` Daniel Barkalow
2009-10-21 3:09 ` Nanako Shiraishi
2009-10-20 20:43 ` Alex Riesen
2009-10-20 22:19 ` Eugene Sajine
2009-10-21 6:25 ` Alex Riesen
2009-10-21 23:32 ` Eugene Sajine
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=81b0412b0910201119w7583487ag276cf964d0a85e@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=euguess@gmail.com \
--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).