archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <>
To: Kevin Daudt <>
Cc: Junio C Hamano <>,
	Arnaud Bertrand <>,
Subject: Re: Mismatch meaning between git-diff and git-log for the .. (double dot notation) and ... (triple dot notation)
Date: Mon, 23 Dec 2019 13:59:28 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20191223182939.GB676947@alpha>

Kevin Daudt wrote:
> On Mon, Dec 23, 2019 at 10:02:31AM -0800, Junio C Hamano wrote:

>> Please unlearn dot-dot and three-dots when using "git diff", which
>> is not about ranges but about comparing two endpoints.  If we were
>> reinventing Git today from scratch, we would make "git diff A..B" an
>> error.  You can consider it a bug that the command accepts a range
>> notation, but this will not change any time soon without a large
>> fight to find and fix uses of the syntax in scripts by longtime Git
>> users have written over the years.
> I agree that you should not use `A..B`, but what is wrong with
> `A...B`? The alternative is a lot more verbose.
> git diff $(git merge-base A B) B

Commands like "git checkout" have been learning a `...` shorthand
which is not much better as far as intuitiveness goes:

	# doesn't work, just here for demonstration
	git diff A...B B

With hindsight, "git diff A..B" would be the perfect spelling for
this, but that would break too many people's muscle memories and
scripts.  Would it make sense to have a commandline option for this?

	# doesn't work, just here for demonstration
	git diff --fork-point A B

A random thought,

  reply	other threads:[~2019-12-23 21:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-23 12:51 Mismatch meaning between git-diff and git-log for the .. (double dot notation) and ... (triple dot notation) Arnaud Bertrand
2019-12-23 18:02 ` Junio C Hamano
2019-12-23 18:29   ` Kevin Daudt
2019-12-23 21:59     ` Jonathan Nieder [this message]
2019-12-23 22:10     ` Junio C Hamano

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

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