Re: Deprecating git diff ..; dealing with other ranges
- Date: Wed, 13 Mar 2019 08:01:42 +0100
- From: Johannes Sixt <j6t@xxxxxxxx>
- Subject: Re: Deprecating git diff ..; dealing with other ranges
Am 12.03.19 um 22:01 schrieb Ævar Arnfjörð Bjarmason:
> On Tue, Mar 12 2019, Andreas Schwab wrote:
>> On Mär 12 2019, Junio C Hamano <gitster@xxxxxxxxx> 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.
Still, your and Andreas's use-case is reason enough *not* to deprecate
diff A..B, IMO.
We wouldn't be able to remove .. wholesale anyway because diff A.. and
diff ..B, where the missing endpoints are filled in with HEAD would have
to live on.