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

Re: [PATCH] git log -g: Complain, but do not fail, when no reflogs are there

From
Alex Riesen <raa.lkml@gmail.com>
Date
Jul 24, 2007, 07:26 UTC
Message-ID
<81b0412b0707240026v4321a709wcbbbd7b67a4c506b@mail.gmail.com>
In-Reply-To
<Pine.LNX.4.64.0707240039300.14781@racer.site>
On 7/24/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
Show 6 quoted lines
>
> When asking "git log -g --all", clearly you want to see only those refs
> that do have reflogs, but you do not want it to fail, either.
>
> So instead of die()ing, complain about it, but move on to the other refs.
>

I believe you wont even see these complaints: the pager will start shortly afterwards and fill the screen with commits, completely hiding the errors.

Previous: Johannes SchindelinNext: Johannes Schindelin
Message 4 of 7 in “git log -g: Complain, but do not fail, when no reflogs are there”
  1. git log -g: Complain, but do not fail, when no reflogs are thereJohannes Schindelin, Jul 23, 2007
  2. Junio C HamanoJul 24, 2007
  3. Johannes SchindelinJul 24, 2007
  4. Alex RiesenJul 24, 2007
  5. Johannes SchindelinJul 24, 2007
  6. Alex RiesenJul 24, 2007
  7. Johannes SchindelinJul 24, 2007

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.