git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: Matt McCutchen <hashproduct+git@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <junkio@cox.net>
Subject: Re: How to view an old revision?
Date: Wed, 01 Nov 2006 14:46:02 +0000	[thread overview]
Message-ID: <4548B32A.5030803@shadowen.org> (raw)
In-Reply-To: <3bbc18d20611010637s6d05aecbt98322b62cf7235e8@mail.gmail.com>

Matt McCutchen wrote:
> On 11/1/06, Andy Whitcroft <apw@shadowen.org> wrote:
>>         git cat-file -p <commit-ish>:<file>
> 
> Nice!  Thanks!  I had guessed "git cat-file -p <commit-ish>/<file>"
> but didn't try a colon as the separator.  The colon syntax ought to be
> mentioned in the git-cat-file man page.

There are some improvements in the documentation in 'next' but nothing
which would make this easier for you to find.

Junio, I wonder if we should be changing the usage for this command
slightly.  Currently, it mearly says <object> as the identifier for the
blob.  Really this is <object-ish> as it supports symbolic naming in
addition to raw sha1's.  I also feel it would be very helpful if
<commit-ish> and family were documented as a glossary section in main
git manpage.

Something like this:

<commit-ish>:: is an sha1 for a commit, or any symbolic name for a
commit (see SPECIFYING REVISIONS in git-rev-parse)

What do people think.  I can do the munging about if its seems like a
sane plan.


  reply	other threads:[~2006-11-01 14:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-01 14:20 How to view an old revision? Matt McCutchen
2006-11-01 14:30 ` Andy Whitcroft
2006-11-01 14:37   ` Matt McCutchen
2006-11-01 14:46     ` Andy Whitcroft [this message]
2006-11-01 16:00       ` Junio C Hamano
2006-11-01 16:25         ` Matt McCutchen
2006-11-01 19:02         ` Andy Whitcroft

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=4548B32A.5030803@shadowen.org \
    --to=apw@shadowen.org \
    --cc=git@vger.kernel.org \
    --cc=hashproduct+git@gmail.com \
    --cc=junkio@cox.net \
    /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).