From: Junio C Hamano <gitster@pobox.com>
To: Brandon Williams <bmwill@google.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Lars Schneider <larsxschneider@gmail.com>,
git@vger.kernel.org, peff@peff.net
Subject: Re: What's cooking in git.git (Apr 2017, #04; Wed, 19)
Date: Thu, 20 Apr 2017 17:56:37 -0700 [thread overview]
Message-ID: <xmqq37d28toa.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170420231836.GM142567@google.com> (Brandon Williams's message of "Thu, 20 Apr 2017 16:18:36 -0700")
Brandon Williams <bmwill@google.com> writes:
> On 04/20, Brandon Williams wrote:
>> On 04/20, Johannes Schindelin wrote:
>> > Hi Lars & Junio,
>> >
>> > On Thu, 20 Apr 2017, Lars Schneider wrote:
>> >
>> > > > * bw/forking-and-threading (2017-04-19) 11 commits
>> > > > - run-command: block signals between fork and execve
>> > > > - run-command: add note about forking and threading
>> > > > - run-command: handle dup2 and close errors in child
>> > > > - run-command: eliminate calls to error handling functions in child
>> > > > - run-command: don't die in child when duping /dev/null
>> > > > - run-command: prepare child environment before forking
>> > > > - string-list: add string_list_remove function
>> > > > - run-command: use the async-signal-safe execv instead of execvp
>> > > > - run-command: prepare command before forking
>> > > > - t0061: run_command executes scripts without a #! line
>
> I just double checked what differences existed between what I have
> locally and what is queued at bw/forking-and-threading and it looks like
> the changes (adding the !MINGW) to just this one patch were missed,
> while the rest of them were picked up. Just and fyi.
Thanks. Queued with a warning in the log message.
next prev parent reply other threads:[~2017-04-21 0:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 5:37 What's cooking in git.git (Apr 2017, #04; Wed, 19) Junio C Hamano
2017-04-20 9:59 ` Duy Nguyen
2017-04-20 15:35 ` Jeff King
2017-04-20 22:51 ` Junio C Hamano
2017-04-20 22:46 ` Junio C Hamano
2017-04-20 15:32 ` Lars Schneider
2017-04-20 22:52 ` Junio C Hamano
[not found] ` <D61D47BD-9750-4FB6-892E-013504E03738@gmail.com>
2017-04-20 13:24 ` Johannes Schindelin
2017-04-20 16:56 ` Brandon Williams
2017-04-20 23:18 ` Brandon Williams
2017-04-21 0:56 ` Junio C Hamano [this message]
2017-04-20 22:58 ` Junio C Hamano
2017-04-21 9:50 ` Johannes Schindelin
2017-04-21 12:29 ` Christian Couder
2017-04-22 11:48 ` Johannes Schindelin
2017-04-22 17:32 ` Christian Couder
2017-04-24 14:08 ` Johannes Schindelin
2017-04-22 13:37 ` Johannes Sixt
2017-04-24 14:24 ` Johannes Schindelin
2017-04-24 16:34 ` Philip Oakley
2017-04-25 2:17 ` Christian Couder
2017-04-25 2:00 ` Christian Couder
2017-04-25 5:51 ` Johannes Sixt
2017-04-25 6:52 ` Junio C Hamano
2017-04-25 18:26 ` Johannes Sixt
2017-04-24 0:25 ` Junio C Hamano
2017-04-24 14:19 ` Johannes Schindelin
2017-04-24 15:18 ` Ævar Arnfjörð Bjarmason
2017-04-25 0:56 ` Junio C Hamano
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=xmqq37d28toa.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=larsxschneider@gmail.com \
--cc=peff@peff.net \
/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.