Re: Deprecating git diff ..; dealing with other ranges
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Mar 12, 2019, 07:17 UTC
- Message-ID
- <xmqqmum0h88n.fsf@gitster-ct.c.googlers.com>
- In-Reply-To
- <20190311093751.GA31092@archbookpro.localdomain>
Denton Liu <liu.denton@gmail.com> writes:
> I was in the process of deprecating `git diff <commit>..<commit>` as > discussed here[1]. > > [1]: https://public-inbox.org/git/xmqqmumy6mxe.fsf@gitster-ct.c.googlers.com/
I didn't (and don't) advocate such a deprecation, FWIW, in that message. I simply do not think it is worth the cost.
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.