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

Re: Bogus error from git log --full-diff

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 19, 2020, 17:13 UTC
Message-ID
<xmqqmu4zhtcn.fsf@gitster.c.googlers.com>
In-Reply-To
<585541592583234@mail.yandex.ru>
Konstantin Tokarev <annulen@yandex.ru> writes:
> I've reported this issue in February on this very list and didn't
> get any reaction from developers.  Seems like it's not considered
> to be a bug.

Please do not read too much into lack of response. It may be caused by many things, including (certainly non-exhaustive):

 (1) the message may have been un-understandable and/or did not look
     interesting enough to ask for clarifications and more info to
     produce a useful response,
 (2) the message may have been delivered in a hostile tone that
     people chose to ignore even though it raised a valid issue, or
 (3) the message was simply missed because everybody was busy doing
     other things.

By default, everybody should assume the last one. Re-raising the issue after some cooling-off period would be a good strategy.

Thanks.
Previous: Konstantin TokarevNext: Junio C Hamano
Message 3 of 4 in “Bogus error from git log --full-diff”
  1. Andreas SchwabJun 19, 2020
  2. Konstantin TokarevJun 19, 2020
  3. Junio C HamanoJun 19, 2020
  4. Junio C HamanoJun 19, 2020

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.