Re: How do get a specific version of a particular file?

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Feb 27, 2007, 19:55 UTC
Message-ID: <Pine.LNX.4.63.0702272053080.22628@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <20070227154241.GA8228@thunk.org>

Hi,

On Tue, 27 Feb 2007, Theodore Tso wrote:

Show 10 quoted lines

> On Tue, Feb 27, 2007 at 01:57:18PM +0100, Johannes Schindelin wrote:
> > git-show, of all, is _not_ plumbing. It is one of the foremost porcelain 
> > programs core Git ships.
> 
> Maybe, but its man page doesn't show it.  The average end-user isn't 
> going to be thinking about blobs, tree objects, and tag objects. 
> Furthermore, the EXAMPLES section in the man page is misformatted due to 
> some ASCII doc issues.  I'll send a patch to correct the EXAMPLES 
> section, but if git-show is a foremost porecelain program the 
> DISCRIPTION section probably needs to be rewritten as well.

Thank you for the patch.

Since you seem to be no old-timer who cannot remember how she learnt about certain Git concepts: What documentation did you read, an in which order? This might help us making the parts likely to be seen by new users better...

Show 8 quoted lines

> > git show v.37:e2fsck/pass1.c
> 
> Thanks, I just didn't know about tree-ish:pathname syntax, and I've
> been playing with git for a while.
> 
> As a suggestion, maybe we should be moving (or at least copying) things 
> like the <object> identifier syntax from the git-rev-parse manpage 
> (which is plumbing, right?) to the top-level git manpage?

My vote is for moving, and referencing (kind of mv && ln -s).

But that means that you have to explain in a really concise way that Git repositories contain blob, tree, commit and tag objects. And what they are.

Ciao, Dscho