git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: How do get a specific version of a particular file?
Date: Tue, 27 Feb 2007 17:39:29 -0500	[thread overview]
Message-ID: <20070227223929.GA9027@thunk.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0702272053080.22628@wbgn013.biozentrum.uni-wuerzburg.de>

On Tue, Feb 27, 2007 at 08:55:41PM +0100, Johannes Schindelin wrote:
> 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...

I started using Everyday git, and the git(7) man page, and the
tutorials.  I tried using some of the git manpages, but many of them
were so inpenetrable that I would just skip over that bit and hope the
rest of the man page would make sense or would just try searching
somewhere for the information.  To be honest, some of the best
documentation was Linus's email messages on the git mailing list,
especially the ones about git philosophy and examples about how to do
things.

For example, the man page of git-rev-parse will give you a very dry
description of ".." and "...", but absolutely no examples of when you
would you might use one or the other.  The only place where I learned
about this was from some of Linus's e-mail messages, and even then I'm
still a little shaky on when you might use '...'.   

And I'm still not sure why

	git show v1.5.0..v1.5.0.1 

doesn't throw an error, and why it prints what it does...

> > 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.

Well, git(7) already has an extraordinary verbose description of glob,
tree, commit, and tag options, so if we move the object id syntax to
git(7) that wouldn't be a problem.  :-)

						- Ted

  reply	other threads:[~2007-02-27 22:39 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 12:34 How do get a specific version of a particular file? Theodore Ts'o
2007-02-27 12:43 ` Christian MICHON
2007-02-27 12:44 ` Peter Baumann
2007-02-27 12:49 ` Alex Riesen
2007-02-27 12:53   ` Alex Riesen
2007-02-27 12:57 ` Johannes Schindelin
2007-02-27 15:42   ` Theodore Tso
2007-02-27 19:55     ` Johannes Schindelin
2007-02-27 22:39       ` Theodore Tso [this message]
2007-02-27 23:25         ` Randal L. Schwartz
2007-02-27 23:35           ` Junio C Hamano
2007-02-28  0:22             ` Linus Torvalds
2007-02-28  0:31               ` Junio C Hamano
2007-02-28  0:39                 ` Johannes Schindelin
2007-02-28  0:54                 ` Linus Torvalds
2007-02-28  1:11                   ` Nicolas Pitre
2007-02-28  1:24                     ` Linus Torvalds
2007-02-28  1:48                       ` Nicolas Pitre
2007-02-28  2:32                 ` Theodore Tso
2007-02-28  2:45                   ` Junio C Hamano
2007-02-28  3:03                     ` Theodore Tso
2007-02-28  4:33                       ` Junio C Hamano
2007-02-28  1:04               ` Nicolas Pitre
2007-02-28  0:01           ` Johannes Schindelin
2007-02-28  0:30             ` Linus Torvalds
2007-02-28  0:33               ` Junio C Hamano
2007-02-28  0:36               ` Johannes Schindelin
2007-02-27 15:43   ` [PATCH] Fix git-show man page formatting in the EXAMPLES section Theodore Tso
2007-02-27 16:38 ` How do get a specific version of a particular file? Linus Torvalds
2007-02-27 17:14   ` Bill Lear
2007-02-27 19:09   ` Theodore Tso
2007-02-27 19:33     ` Linus Torvalds

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=20070227223929.GA9027@thunk.org \
    --to=tytso@mit.edu \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    /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).