git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Sajine <euguess@gmail.com>
To: git@vger.kernel.org
Cc: Eugene Sajine <euguess@gmail.com>
Subject: "git log -- SHA-1" - how to get/simulate this functionality?
Date: Mon, 26 Apr 2010 13:54:25 -0400	[thread overview]
Message-ID: <i2o76c5b8581004261054h591c266fre1a0dd87cd8511e1@mail.gmail.com> (raw)

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)
The current way seems to be a bit cumbersome

git log --no-abbrev --raw --all | grep SHA-1

parse for path(s) and then git log -- path...

I would want something like git log -- SHA-1

Any ideas?

Thanks,
Eugene

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

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