From: Andy Whitcroft <apw@shadowen.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] document the <tree ish> <file> blob reference syntax
Date: Wed, 25 Oct 2006 20:40:26 +0100 [thread overview]
Message-ID: <453FBDAA.50305@shadowen.org> (raw)
In-Reply-To: <7vwt6ob5zc.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Andy Whitcroft <apw@shadowen.org> writes:
>
>> It is possible to specify a specific file within a tree-ish
>> symbolically. For example you can find the contents of
>> a specific file in a specific commit as below:
>>
>> git cat-file -p v1.2.4:git-prune.sh
>
> Didn't we document this elsewhere recently in git-rev-parse?
> How about this instead?
>
> -- >8 --
> [PATCH] Refer to git-rev-parse:Specifying Revisions from git.txt
>
> The brief list given in "Symbolic Identifiers" section of the
> main documentation is good enough for overview, but help the
> reader to find a more comrehensive list as needed.
>
> Signed-off-by: Junio C Hamano <junkio@cox.net>
> ---
> Documentation/git.txt | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/git.txt b/Documentation/git.txt
> index 3af6fc6..b00607e 100644
> --- a/Documentation/git.txt
> +++ b/Documentation/git.txt
> @@ -562,6 +562,9 @@ HEAD::
> a valid head 'name'
> (i.e. the contents of `$GIT_DIR/refs/heads/<head>`).
>
> +For a more complete list of ways to spell object names, see
> +"SPECIFYING REVISIONS" section in gitlink:git-rev-parse[1].
> +
That section seems to have more compresensive descriptions of the
various definitions of commit-ish, but not a tree-ish. Specifically,
there is no mentions of tree-ish:file
next prev parent reply other threads:[~2006-10-25 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 10:42 [PATCH] document the <tree ish> <file> blob reference syntax Andy Whitcroft
2006-10-25 18:33 ` Junio C Hamano
2006-10-25 19:40 ` Andy Whitcroft [this message]
2006-10-25 20:13 ` Junio C Hamano
2006-10-25 20:04 ` Jakub Narebski
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=453FBDAA.50305@shadowen.org \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.