Junio C Hamano wrote: > Andy Whitcroft <apw@xxxxxxxxxxxx> 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@xxxxxxx> > --- > 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 -apw - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html