git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [Bug report] git diff stat shows unrelated diff

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 17, 2019, 03:34 UTC
Message-ID
<xmqq1s473x63.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<dca9622d-c8e7-abcb-2e13-73bd8bb9dd84@iee.org>
Philip Oakley <philipoakley@iee.org> writes:
Show 14 quoted lines
>> Those who do *not* opt into that "early warning" configuration dance
>> would eventually be warned whenever they type "diff A..B", and the
>> timing for that eventuality is not under their control, so quite
>> honestly, I do not see much point in "giving users the chance".
>
> With the opposite hat on, not giving users the choice does seem unfair
> to those that are trying to keep up. If we are warning (in the release
> notes) of an upcoming deprecation (in the code) then it does seem
> helpful that users could buy into the deprecation early, and at their
> convenience, to assist in the unlearning of an old habit, which can be
> much harder than learning a new habit, hence my comment.
>
> You are right that those who neither notice nor care will be surprised
> later, but we shouldn't let that limit others.

I still do not quite get where you are coming from. Are you saying that those who do not opt into the early warning may get 2 cycles (just picked out of thin-air) of deprecation period, and with an optional early warning feature, those who feel that 2 cycles is not long enough to train their fingers would spend 3 cycles and they will be helped than without?

That line of thinking sounds somewhat ridiculous---where does it end? If those who opt into would find it sufficient to have 3 cycles to train, there may still be people who feel 3 is not enough and want to have 4. As we make it longer, we'd cover more people and at some point we'd reach the point of diminishing returns.

Wouldn't it be even better, and far simper, to just extend the deprecation period to that many cycles to make it long enough for majority of users' needs, without any early warning option?

The thing is, once you train your fingers, it does not matter to you if the deprecation warning is still there, as you'd not be typing "diff A..B" at that point. So I am not sure who you are trying to help by the early warning option.

Thanks.
Previous: Philip OakleyNext: Philip Oakley
Message 11 of 17 in “[Bug report] git diff stat shows unrelated diff”
  1. Viresh KumarFeb 14, 2019
  2. Johannes SixtFeb 14, 2019
  3. Elijah NewrenFeb 14, 2019
  4. Junio C HamanoFeb 14, 2019
  5. Denton LiuFeb 15, 2019
  6. Elijah NewrenFeb 15, 2019
  7. Junio C HamanoFeb 15, 2019
  8. Philip OakleyFeb 15, 2019
  9. Junio C HamanoFeb 15, 2019
  10. Philip OakleyFeb 16, 2019
  11. Junio C HamanoFeb 17, 2019
  12. Philip OakleyFeb 17, 2019
  13. Junio C HamanoFeb 18, 2019
  14. Junio C HamanoFeb 15, 2019
  15. Viresh KumarFeb 15, 2019
  16. Elijah NewrenFeb 15, 2019
  17. Viresh KumarFeb 18, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.