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

Re: print errors from git-update-ref

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jul 27, 2006, 11:04 UTC
Message-ID
<Pine.LNX.4.63.0607271302150.29667@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<20060727012856.GB32492@spearce.org>
Hi,
On Wed, 26 Jul 2006, Shawn Pearce wrote:
> This change adds a test for trying to create a ref within a directory
> that is actually currently a file, and adds error printing within
> the ref locking routine should the resolve operation fail.

Why not just print an error message when the resolve operation fails, instead of special casing this obscure corner case? It is way shorter, too. The test should stay, though.

Ciao, Dscho

Previous: Shawn PearceNext: Shawn Pearce
Message 4 of 7 in “print errors from git-update-ref”
  1. Alex RiesenJul 18, 2006
  2. Junio C HamanoJul 24, 2006
  3. Shawn PearceJul 27, 2006
  4. Johannes SchindelinJul 27, 2006
  5. Shawn PearceJul 28, 2006
  6. Junio C HamanoJul 28, 2006
  7. Shawn PearceJul 29, 2006

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.