From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: js/bisect-in-c, was Re: What's cooking in git.git (Aug 2022, #05; Mon, 15)
Date: Wed, 17 Aug 2022 13:05:03 -0700 [thread overview]
Message-ID: <xmqq35duvdow.fsf@gitster.g> (raw)
In-Reply-To: <CABPp-BHBOqnU7DSLkYPig=c6+emWGaE1vdzaPk0D90yQdof+6A@mail.gmail.com> (Elijah Newren's message of "Wed, 17 Aug 2022 12:24:57 -0700")
Elijah Newren <newren@gmail.com> writes:
> Ah, gotcha. My impression was that the exit codes did match what the
> previous shell code had done, but didn't match what other builtins
> usually return. Perhaps I misread those discussion comments.
Or perhaps I did ;-)
The topic has been waiting for the finishing polish for so long that
I do not remember the details of the discussion offhand, certainly
not better than I did when I left the note in the "What's cooking"
report.
next prev parent reply other threads:[~2022-08-17 20:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 21:24 What's cooking in git.git (Aug 2022, #05; Mon, 15) Junio C Hamano
2022-08-16 8:56 ` js/bisect-in-c, was " Johannes Schindelin
2022-08-17 1:26 ` Elijah Newren
2022-08-17 6:27 ` Johannes Schindelin
2022-08-17 18:57 ` Junio C Hamano
2022-08-17 19:24 ` Elijah Newren
2022-08-17 20:05 ` Junio C Hamano [this message]
2022-08-19 11:04 ` Johannes Schindelin
2022-08-19 14:40 ` Ævar Arnfjörð Bjarmason
2022-08-16 16:00 ` sy/mv-out-of-cone (was Re: What's cooking in git.git (Aug 2022, #05; Mon, 15)) Victoria Dye
2022-08-16 16:16 ` Junio C Hamano
2022-08-17 2:03 ` Shaoxuan Yuan
2022-08-17 0:36 ` cw/submodule-merge-messages (Was: " Elijah Newren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq35duvdow.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.