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

Re: [PATCH] lock_any_ref_for_update(): clarify switch case statement

From
Junio C Hamano <gitster@pobox.com>
Date
May 10, 2011, 20:07 UTC
Message-ID
<7vliyeiaju.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4DC925F1.4060307@elegosoft.com>
Michael Schubert <mschub@elegosoft.com> writes:
> Write CHECK_REF_FORMAT_OK instead of '0' to be more verbose.

It is not wrong per-se to spell it out to be more descriptive, but I would think 0 is clear enough that there is no error.

In any case, being verbose is never a goal ;-).
Previous: Michael Schubert
Message 2 of 2 in “lock_any_ref_for_update(): clarify switch case statement”
  1. lock_any_ref_for_update(): clarify switch case statementMichael Schubert, May 10, 2011
  2. Junio C HamanoMay 10, 2011

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.