Re: ident hash usage question

From: Eugene Sajine <euguess@gmail.com>
Date: Oct 20, 2009, 18:59 UTC
Message-ID: <76c5b8580910201159i75a90f28pb882e83f0c7c40ae@mail.gmail.com>
In-Reply-To: <81b0412b0910201119w7583487ag276cf964d0a85e@mail.gmail.com>

Show 6 quoted lines

>
> 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
>

This is exactly what I was looking for! Thank you!

I understand that in some cases this can give me two paths instead of one, but it will only demonstrate that I have absolute copy of a file inside my repo, which is also good to diagnose (because the probability of having two meaningful files with the same hash, but different content is way too low).

So, this means that after few little tricks the keyword expansion problem may be resolved by only using $Id$ keyword. Because after having this hash one can build up all necessary info from it:

#finding blobs with SHA indicated in $Id$ keword $ git log --no-abbrev --raw --all | grep SHA-1

# little script or regexp here (don’t have it) $ pull out path from result

# last commit for the path with all corresponding info $ git log -1 HEAD path

So, this seems to cover most of the needs of people who would like to use keywords expansion, if they are not ready to forget about them…

Does it make sense?

Thanks, Eugene