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

Re: git log -g bizarre behaviour

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 2, 2016, 20:42 UTC
Message-ID
<xmqqa8nisv2r.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<1454444532.2713.1.camel@kaarsemaker.net>
Dennis Kaarsemaker <dennis@kaarsemaker.net> writes:
Show 6 quoted lines
>> > $ git (log -g|reflog) v2.7.0
>> > From the bizarre behaviour above to a silent noop.
>
> As I demonstrated in the text that you cut: that is not true.
> git log -g v2.7.0 and git reflog v2.7.0 are *not* silent, but buggy. I
> would like to make them silent.

Ah, sorry, I totally misread your "bizarre". Yes, "log -g" that walks the history not the reflog is "bizarre" and wrong, which we already agreed in the previous exchange. A fixed behaviour that walks only the reflog entries should become a "silent noop".

Previous: Dennis KaarsemakerNext: Dennis Kaarsemaker
Message 6 of 10 in “git log -g bizarre behaviour”
  1. Dennis KaarsemakerJan 31, 2016
  2. Junio C HamanoFeb 1, 2016
  3. Dennis KaarsemakerFeb 2, 2016
  4. Junio C HamanoFeb 2, 2016
  5. Dennis KaarsemakerFeb 2, 2016
  6. Junio C HamanoFeb 2, 2016
  7. log -g: ignore revision parameters that have no reflogDennis Kaarsemaker, Feb 2, 2016
  8. Junio C HamanoFeb 3, 2016
  9. Dennis KaarsemakerFeb 3, 2016
  10. Junio C HamanoFeb 3, 2016

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.