From: "Eckhard Maaß" <eckhard.s.maass@googlemail.com>
To: Denton Liu <liu.denton@gmail.com>
Cc: "Robert Dailey" <rcdailey.lists@gmail.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Eckhard Maaß" <eckhard.s.maass@googlemail.com>,
Git <git@vger.kernel.org>
Subject: Re: Merge commit diff results are confusing and inconsistent
Date: Tue, 7 May 2019 17:55:05 +0200 [thread overview]
Message-ID: <20190507155505.GA31344@esm> (raw)
In-Reply-To: <20190507145849.GA6313@archbookpro.localdomain>
On Tue, May 07, 2019 at 10:58:49AM -0400, Denton Liu wrote:
> For more details, this code[2] just blindly diffs the first two
> endpoints returned preceding `repo_init_revisions`.
If you throw in more than two endpoints, the result is a combined diff
with respect to the first commit. You can have some fun with that, eg
"git diff -c @ @~4 @^^2~4".
> Also, not to rehash an old discussion but I'll let this thread be my
> argument *against* allowing range-notation in git-diff.
Well, I think the most confusing part is to have this undocumented
around. The range notation are basically just the same symbols for
git-diff, but the meaning seems to be quite different. If this is going
to stay - shouldn't there be at least some documentation for people
trying such stuff out? And that we can point to? Or is there a reason to
keep this undocumented?
Greetings,
Eckhard
next prev parent reply other threads:[~2019-05-07 15:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 15:55 Merge commit diff results are confusing and inconsistent Robert Dailey
2019-05-03 19:12 ` Eckhard Maaß
2019-05-06 15:38 ` Robert Dailey
2019-05-06 16:52 ` Eckhard Maaß
2019-05-06 23:52 ` Ævar Arnfjörð Bjarmason
2019-05-07 14:10 ` Robert Dailey
2019-05-07 14:41 ` Robert Dailey
2019-05-07 14:58 ` Denton Liu
2019-05-07 15:55 ` Eckhard Maaß [this message]
2019-05-07 15:26 ` Ævar Arnfjörð Bjarmason
2019-05-07 16:44 ` Elijah Newren
2019-05-11 14:08 ` Philip Oakley
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=20190507155505.GA31344@esm \
--to=eckhard.s.maass@googlemail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=liu.denton@gmail.com \
--cc=rcdailey.lists@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.