From: Eugene Sajine <euguess@gmail.com>
Date: Mon, 26 Apr 2010 18:22:45 GMT
Subject: Re: "git log -- SHA-1" - how to get/simulate this functionality?
Message-ID: <p2y76c5b8581004261122g8e2950fci507cc9090a865843@mail.gmail.com>
In-Reply-To: <z2m81b0412b1004261108n5453b5d2h179a944fa8db9b49@mail.gmail.com>

On Mon, Apr 26, 2010 at 2:08 PM, Alex Riesen <raa.lkml@gmail.com> wrote:
> On Mon, Apr 26, 2010 at 19:56, Eugene Sajine <euguess@gmail.com> wrote:
>> On Mon, Apr 26, 2010 at 1:54 PM, Eugene Sajine <euguess@gmail.com> wrote:
>>> Hi,
>>>
>>> I'm wondering if there is a way to get some repo information if the
>>> only thing i know is SHA-1 (no full path to the file)
>>
>> I mean of course the SHA-1 of the blob, i.e. the result of git
>> hash-object some_file
>
> Try 'git cat-file -t <sha>'. It prints what object type is under the hash.
> Than you can use either 'git cat-file <type> <sha>' (the most precise version,
> which shall fail if anything is wrong), 'git cat-file -p <sha>' or plain
> 'git show <sha>' (which always works, unless repo's broken).
>

Well thank you for that, but that gives me what i already know - the content.
I need to "reverse engineer" the history by having only the content
and its SHA-1 in order to indentify the last commitID and get all
relevant info (author, date etc. )

This is all about avoiding using keyword expansion (thanks CVS for bad habbits)

Thanks,
Eugene