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

Exit code of git-ls-remote

From
Kacper Kornet <draenog@pld-linux.org>
Date
May 12, 2011, 12:05 UTC
Message-ID
<20110512120536.GA22033@camk.edu.pl>

git-ls-remote behaves differently then git-show-ref when it cannot find any matching refs. While the latter returns non zero exit code in this case, the former always returns 0. Is there any specific reason for this behaviour?

-- 
  Kacper Kornet
Next: Junio C Hamano
Message 1 of 10 in “Exit code of git-ls-remote”
  1. Kacper KornetMay 12, 2011
  2. Junio C HamanoMay 12, 2011
  3. Junio C HamanoMay 12, 2011
  4. ls-remote: optionally return non-zero on non-existing refsMichael Schubert, May 18, 2011
  5. Thiago FarinaMay 18, 2011
  6. Junio C HamanoMay 18, 2011
  7. ls-remote: optionally return non-zero on non-existing refsMichael Schubert, May 18, 2011
  8. Andreas SchwabMay 18, 2011
  9. Junio C HamanoMay 18, 2011
  10. Michael SchubertMay 18, 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.