Why usage function exit with code 129?

5 messages, 2 authors, 2016-06-15 · open the first message on its own page

Why usage function exit with code 129?

From: 徐迪 <hidden>
Date: 2016-06-15 22:52:44

I did like this:
$ git add --foo
$ echo $?
what I got is 129, should this code being used as program terminated
due to a signal? Cause it's 128+1. According to this[1].

[1] http://tldp.org/LDP/abs/html/exitcodes.html

Re: Why usage function exit with code 129?

From: Nguyen Thai Ngoc Duy <hidden>
Date: 2016-06-15 22:52:44

2012/1/6 徐迪 [off-list ref]:
I did like this:
$ git add --foo
$ echo $?
what I got is 129, should this code being used as program terminated
due to a signal? Cause it's 128+1. According to this[1].
usage() (in your case) always returns 129, die() 128. See 5d1a5c0
([PATCH] Better error reporting for "git status")
[1] http://tldp.org/LDP/abs/html/exitcodes.html
No it does not mean terminated by signals.
-- 
Duy

Re: Why usage function exit with code 129?

From: 徐迪 <hidden>
Date: 2016-06-15 22:52:44

quoted
[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?

Re: Why usage function exit with code 129?

From: Nguyen Thai Ngoc Duy <hidden>
Date: 2016-06-15 22:52:44

2012/1/6 徐迪 [off-list ref]:
quoted
quoted
[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

Re: Why usage function exit with code 129?

From: 徐迪 <hidden>
Date: 2016-06-15 22:52:44

在 2012年1月6日 下午4:11,Nguyen Thai Ngoc Duy [off-list ref] 写道:
2012/1/6 徐迪 [off-list ref]:
quoted
quoted
quoted
[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
Ok, that sounds logical.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help