git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Sajine <euguess@gmail.com>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: git@vger.kernel.org, Eugene Sajine <euguess@gmail.com>
Subject: Re: "git log -- SHA-1" - how to get/simulate this functionality?
Date: Mon, 26 Apr 2010 14:22:45 -0400	[thread overview]
Message-ID: <p2y76c5b8581004261122g8e2950fci507cc9090a865843@mail.gmail.com> (raw)
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

  reply	other threads:[~2010-04-26 18:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 17:54 "git log -- SHA-1" - how to get/simulate this functionality? Eugene Sajine
2010-04-26 17:56 ` Eugene Sajine
2010-04-26 18:08   ` Alex Riesen
2010-04-26 18:22     ` Eugene Sajine [this message]
2010-04-26 18:57       ` Alex Riesen
2010-04-26 19:37         ` Alex Riesen
2010-04-26 20:07           ` 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=p2y76c5b8581004261122g8e2950fci507cc9090a865843@mail.gmail.com \
    --to=euguess@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=raa.lkml@gmail.com \
    /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).