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

Re: [PATCH] refs: print errno for read_raw_ref if GIT_TRACE_REFS is set

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 13, 2021, 20:08 UTC
Message-ID
<xmqqy2dmkkvo.fsf@gitster.g>
In-Reply-To
<CAFQ2z_MnZOfo4Bt6SsRJnL+F70r9wr_jYSf2KGvcvyX-8PfVRQ@mail.gmail.com>
Han-Wen Nienhuys <hanwen@google.com> writes:
Show 5 quoted lines
>> I do wonder if we want strerror(errno) instead of the number, but I
>> can go either way (it's just a trace output).
>
> For tracing, it would be most useful if we got the actual symbol (eg.
> ENOENT). Is there a way to get at that?
I do not think there is.

And that is the reason why we see everywhere calls to die_errno(), error(..., strerror(errno)), etc.

As this is interpolated into trace with untranslated string, I suspect that strerror() is not a good match, so let's live with %d for now.

Thanks.
Previous: Han-Wen NienhuysNext: Han-Wen Nienhuys
Message 5 of 7 in “refs: print errno for read_raw_ref if GIT_TRACE_REFS is set”
  1. refs: print errno for read_raw_ref if GIT_TRACE_REFS is setHan-Wen Nienhuys via GitGitGadget, Apr 12, 2021
  2. Junio C HamanoApr 12, 2021
  3. Han-Wen NienhuysApr 13, 2021
  4. Han-Wen NienhuysApr 13, 2021
  5. Junio C HamanoApr 13, 2021
  6. Han-Wen NienhuysApr 23, 2021
  7. refs: print errno for read_raw_ref if GIT_TRACE_REFS is setHan-Wen Nienhuys via GitGitGadget, Apr 13, 2021

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.