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

Re: Why usage function exit with code 129?

From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date
Jan 6, 2012, 08:11 UTC
Message-ID
<CACsJy8D8uKGhtg4zjbHsJCGmqjTwodzFmAZ5w=aUx9CdadVAfw@mail.gmail.com>
In-Reply-To
<CAMocUqSmes+x_tkP6V0OM5rQ5wDGmMm=Q2MFBPhz6Qvzz_SOTg@mail.gmail.com>
2012/1/6 徐迪 <xudifsd@gmail.com>:
Show 9 quoted lines
>>> [1] http://tldp.org/LDP/abs/html/exitcodes.html
>>
>> No it does not mean terminated by signals.
>> --
> In that case, why not just use another code instead of the code that
> leads misunderstanding? I mean, as far as I know, exit code between
> 129 and 255 are used to indicate the program terminated by signal. So
> that usage function can only exit with code between 1 and 127. Am I
> wrong?

Because that code has been there too long (since 2005) any probably all git commands, including plumbing ones, rely on it. Changing it now may break existing scripts.

-- 
Duy
Previous: 徐迪Next: 徐迪
Message 4 of 5 in “Why usage function exit with code 129?”
  1. 徐迪Jan 6, 2012
  2. Nguyen Thai Ngoc DuyJan 6, 2012
  3. 徐迪Jan 6, 2012
  4. Nguyen Thai Ngoc DuyJan 6, 2012
  5. 徐迪Jan 6, 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.