git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Junio C Hamano <junkio@cox.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	"Randal L. Schwartz" <merlyn@stonehenge.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	git@vger.kernel.org
Subject: Re: How do get a specific version of a particular file?
Date: Tue, 27 Feb 2007 21:32:08 -0500	[thread overview]
Message-ID: <20070228023208.GC2178@thunk.org> (raw)
In-Reply-To: <7vejob9l70.fsf@assigned-by-dhcp.cox.net>

On Tue, Feb 27, 2007 at 04:31:47PM -0800, Junio C Hamano wrote:
> Back to serious my self, I am wondering if this is a sensible
> thing to ask:
> 
> 	$ git show master...maint
> 
> which your patch now forbids.

Well, the other design alternative is to make git-show take a list of
objects, so that

	git show v1.5.0..v1.5.0.1

ends up displaying the same thing as

	git show `git-rev-list v1.5.0..v1.5.0.1`

... but I'm not really convinced that's really all that useful.  

Also, at the moment the git-show man page states the following:

       <object>
              The name of the object to show. For a more complete list of ways
              to spell object names, see  "SPECIFYING  REVISIONS"  section  in
              git-rev-parse(1).

Note the use of singular.  That would imply that it takes a single
object, and not a range of objects.  Of course, if the above behavior
were actually shown to be useful, man pages can always be easily
changed.  :-)

						- Ted

  parent reply	other threads:[~2007-02-28  2:32 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
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 [this message]
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=20070228023208.GC2178@thunk.org \
    --to=tytso@mit.edu \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=merlyn@stonehenge.com \
    --cc=torvalds@linux-foundation.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).