From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Randal L. Schwartz" <merlyn@stonehenge.com>,
Theodore Tso <tytso@mit.edu>,
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 16:31:47 -0800 [thread overview]
Message-ID: <7vejob9l70.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0702271605290.12485@woody.linux-foundation.org> (Linus Torvalds's message of "Tue, 27 Feb 2007 16:22:52 -0800 (PST)")
Linus Torvalds <torvalds@linux-foundation.org> writes:
>> > OK, how is that different from git-diff ?
>>
>> I do not think there is any difference. "show" is about
>> multiple points, not ranges. "diff" is about multiple
>> (typically two) points, and not ranges.
>
> Well, I do think Ted has a good point. Having negative refs makes no sense
> for the "no-walk" case (aka "git show").
>
> ... Negative object refs really don't make any sense unless you walk
> the object list (or you're "git diff" and know about ranges explicitly).
If you did not say "(or you're..." part, then I would agree
to this 100%.
On the other hand, as you earlier said:
On Fri, 22 Dec 2006,...
>
> I can understand the advantage of a shortcut like "git diff ..next",
> ...
I can't understand why people complain about this.
YOU DON'T HAVE TO USE IT.
...
> But, really, I still don't understand exactly _what_ "diff a..b" even
> means. Can you explain it to me?
It means exactly the same as "diff a b".
It's that simple.
which made me lol, I am very tempted to say:
It means exactly the same as "show a b".
It's that simple.
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.
next prev parent reply other threads:[~2007-02-28 0:31 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 [this message]
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=7vejob9l70.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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).