From: "Ævar Arnfjörð Bjarmason" <firstname.lastname@example.org>
To: Elijah Newren <email@example.com>
Cc: Andreas Schwab <firstname.lastname@example.org>,
Junio C Hamano <email@example.com>,
Denton Liu <firstname.lastname@example.org>,
Git Mailing List <email@example.com>,
Philip Oakley <firstname.lastname@example.org>,
Viresh Kumar <email@example.com>,
Vincent Guittot <firstname.lastname@example.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: Deprecating git diff ..; dealing with other ranges
Date: Mon, 18 Mar 2019 18:59:01 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
On Mon, Mar 18 2019, Elijah Newren wrote:
> On Tue, Mar 12, 2019 at 2:01 PM Ævar Arnfjörð Bjarmason
> <firstname.lastname@example.org> wrote:
>> On Tue, Mar 12 2019, Andreas Schwab wrote:
>> > On Mär 12 2019, Junio C Hamano <email@example.com> wrote:
>> >> I however think it may be worth making sure that our docs do not
>> >> encourage "diff A..B" and teach "diff A B" when comparing two
>> >> endpoints. That can be done without changing anything in the code.
>> > The nice thing about "diff A..B" is that you can c&p the output from the
>> > fetch run without the need to edit it.
>> Not to shoot down this effort, just to add another similar thing I do
>> regularly for ff-branches:
>> 1. Copy/paste A..B fetch output
>> 2. git log A..B
>> 3. ^log^diff
>> I.e. I just need to tell my terminal to re-run the same "log" command
>> with "diff" instead of "log".
>> Of course as covered in the linked thread it doesn't work for some
>> (non-ff) cases, and I'll sometimes end up cursing it and swapping around
>> ".." for "..." with log/diff.
> Doesn't this somewhat imply that although you use diff A..B here for
> convenience, that it's actually wrong since what you really want is
Yeah "..." would be more correct, but usually when I do this it's for
things where the LHS hasn't diverged.
> Or said another way, the end goal of deprecating "diff "A..B"
> then later reinstating "diff A..B" to mean the same thing as "diff
> A...B" would actually be better even for your usecase?
Yeah, it would be. Sometimes I need to go back and tweak it to be "..."
instead of ".." now. When the two have different behavior I usually want
> Of course, switching to the removal period may just be too painful for
> too many folks since there are obviously people that use it, but I
> just want to see if I'm understanding correctly here.
I think we'd ideally migrate, but the conversion might be too
painful. Junio doesn't seem excited in
I'm not claiming that this ^log^diff use-case is common or anything,
just noting a use-case I do use occasionally and mostly works now.
next prev parent reply other threads:[~2019-03-18 17:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 9:37 Deprecating git diff ..; dealing with other ranges Denton Liu
2019-03-11 13:19 ` Johannes Schindelin
2019-03-11 15:34 ` Elijah Newren
2019-03-12 7:17 ` Junio C Hamano
2019-03-12 17:24 ` Andreas Schwab
2019-03-12 21:01 ` Ævar Arnfjörð Bjarmason
2019-03-13 7:01 ` Johannes Sixt
2019-03-18 17:07 ` Elijah Newren
2019-03-18 17:11 ` Michal Suchánek
2019-03-18 18:51 ` Elijah Newren
2019-03-18 17:59 ` Ævar Arnfjörð Bjarmason [this message]
2019-03-13 1:20 ` Duy Nguyen
2019-03-13 18:12 ` Andreas Schwab
2019-03-12 7:22 ` Junio C Hamano
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:
List information: http://vger.kernel.org/majordomo-info.html
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).