From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Denton Liu <liu.denton@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Philip Oakley <philipoakley@iee.org>,
Elijah Newren <newren@gmail.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
vincent.guittot@linaro.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: Deprecating git diff ..; dealing with other ranges
Date: Tue, 12 Mar 2019 22:01:38 +0100 [thread overview]
Message-ID: <87wol3bydp.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <87va0orop4.fsf@igel.home>
On Tue, Mar 12 2019, Andreas Schwab wrote:
> On Mär 12 2019, Junio C Hamano <gitster@pobox.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.
next prev parent reply other threads:[~2019-03-12 21:01 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 [this message]
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
2019-03-13 1:20 ` Duy Nguyen
2019-03-13 18:12 ` Andreas Schwab
2019-03-12 7:22 ` 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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 \
--in-reply-to=87wol3bydp.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=liu.denton@gmail.com \
--cc=newren@gmail.com \
--cc=philipoakley@iee.org \
--cc=schwab@linux-m68k.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).