Thread (4 messages) flat view 4 messages, 4 authors, 2016-06-15

Re: git bisect code 125 - "WFT?"

From: Piotr Krukowiecki <hidden>
Date: 2016-06-15 22:50:47

On Wed, Mar 16, 2011 at 10:36 PM, Junio C Hamano [off-list ref] wrote:
Piotr Krukowiecki [off-list ref] writes:
quoted
Opinions? Would it be possible to change the meaning of the codes now
(in 1.8.0)?
How about just documenting why it is a bad idea to use 126 or 127 as you
found out somewhere, and stopping there, iow, without changing the code to
use 126/127 that we consider it is a bad idea to use and avoided using so
far?
Documenting it won't help. If you get 126 code, you won't know if user
returned it to mark the code as bad, or if bash returned it to say
that it can't
execute a command.

Of course if changing the meaning is out of option it's better to document
then not to document.

-- 
Piotr Krukowiecki
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help