From: "Matt McCutchen" <hashproduct+git@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: "Andy Whitcroft" <apw@shadowen.org>, git@vger.kernel.org
Subject: Re: How to view an old revision?
Date: Wed, 1 Nov 2006 11:25:35 -0500 [thread overview]
Message-ID: <3bbc18d20611010825ha4063d6wacf4f997d4652d35@mail.gmail.com> (raw)
In-Reply-To: <7vzmbb2m42.fsf@assigned-by-dhcp.cox.net>
On 11/1/06, Junio C Hamano <junkio@cox.net> wrote:
> I was actually reviewing the documentation of git-rev-parse and
> noticed that it talks about naming objects in the section called
> "SPECIFYING REVISIONS". The title implies that it is about
> committish (because we think of "revisions" as something that is
> used in walking commit ancestry chains), but it actually talks
> about naming objects of any type.
There's no way I would have known to look in git-rev-parse. My
git-rev-parse man page doesn't mention the colon syntax, but now I see
that part in git's gitweb; my man page must be too old. Either (1) or
(2) would have been enough for me to figure out that the colon syntax
would do what I wanted, but to grab the attention of the less
persistent user, it would be good to mention the particular case of
"git-cat-file <commit-ish>:<file>" in the git-cat-file man page.
next prev parent reply other threads:[~2006-11-01 16:25 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
2006-11-01 16:00 ` Junio C Hamano
2006-11-01 16:25 ` Matt McCutchen [this message]
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=3bbc18d20611010825ha4063d6wacf4f997d4652d35@mail.gmail.com \
--to=hashproduct+git@gmail.com \
--cc=apw@shadowen.org \
--cc=git@vger.kernel.org \
--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).