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

Re: git config error message

From
Andreas Schwab <schwab@linux-m68k.org>
Date
Oct 27, 2012, 13:14 UTC
Message-ID
<m2d3049hvs.fsf@igel.home>
In-Reply-To
<CAB9Jk9COSZOske5xzgnE=1oHe7qiwwOzHYE6pJkuZ0sZyZYhng@mail.gmail.com>
Angelo Borsotti <angelo.borsotti@gmail.com> writes:
> Besides that, it is common practice in *nix OSs to
> consider a return != 0 as an error.

Is grep not finding a match an error? Is cmp finding a difference an error? It all depends on the context.

> How can otherwise the user tell a corrupted configuration file from a
> missing key?

You cannot, as long as your configuration file is well-formed, because a missing key is an expected condition in many cases.

Andreas.
-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Previous: Angelo BorsottiNext: Angelo Borsotti
Message 7 of 9 in “git config error message”
  1. Angelo BorsottiOct 27, 2012
  2. Andreas SchwabOct 27, 2012
  3. Angelo BorsottiOct 27, 2012
  4. Andreas SchwabOct 27, 2012
  5. Ben WaltonOct 27, 2012
  6. Angelo BorsottiOct 27, 2012
  7. Andreas SchwabOct 27, 2012
  8. Angelo BorsottiOct 27, 2012
  9. Andreas SchwabOct 27, 2012

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.