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

Re: git bisect code 125 - "WFT?"

From
Piotr Krukowiecki <piotr.krukowiecki@gmail.com>
Date
Mar 16, 2011, 22:06 UTC
Message-ID
<AANLkTikRttGnxex1CYSQnSg4PgctFj0-qNjf5un+fL0W@mail.gmail.com>
In-Reply-To
<7v1v267no9.fsf@alter.siamese.dyndns.org>
On Wed, Mar 16, 2011 at 10:36 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 9 quoted lines
> Piotr Krukowiecki <piotr.krukowiecki@gmail.com> writes:
>
>> 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
Previous: Junio C HamanoNext: Johannes Sixt
Message 3 of 8 in “git bisect code 125 - "WFT?"”
  1. Piotr KrukowieckiMar 16, 2011
  2. Junio C HamanoMar 16, 2011
  3. Piotr KrukowieckiMar 16, 2011
  4. Johannes SixtMar 17, 2011
  5. Jeff KingMar 17, 2011
  6. Junio C HamanoMar 17, 2011
  7. 1/2 git bisect run: exit code 126 and 127 abort the runPiotr Krukowiecki, Mar 19, 2011
  8. 2/2 bisect documentation: exit codes 126,127 abort bisectPiotr Krukowiecki, Mar 19, 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.