From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: mr/bisect-in-c-2, was Re: What's cooking in git.git (Jul 2020, #01; Mon, 6)
Date: Wed, 08 Jul 2020 16:11:25 -0700 [thread overview]
Message-ID: <xmqqy2ntzjoi.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <xmqq36622eru.fsf@gitster.c.googlers.com> (Junio C. Hamano's message of "Wed, 08 Jul 2020 08:43:49 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
>>> Rewrite of the remainder of "git bisect" script in C continues.
>>>
>>> Expecting a response to reviews.
>>> cf. <nycvar.QRO.7.76.6.2005230007260.56@tvgsbejvaqbjf.bet>
>>
>> Maybe you could change this to
>>
>> Needs more reviews.
>> cf. <20200701133504.18360-1-mirucam@gmail.com>
>>
>> ?
>
> Thanks, absolutely.
Actually, the state was before that. It would have been "Reroll exists"
with the same reference.
In any case, the latest one broke build of 'seen' and I had to
exclude it from the day's integration. Now it should be listed
as "Needs more work" or something.
next prev parent reply other threads:[~2020-07-08 23:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 5:57 What's cooking in git.git (Jul 2020, #01; Mon, 6) Junio C Hamano
2020-07-07 13:29 ` sg/commit-graph-cleanups (was Re: What's cooking in git.git (Jul 2020, #01; Mon, 6)) Derrick Stolee
2020-07-07 15:10 ` Junio C Hamano
2020-07-07 15:12 ` Junio C Hamano
2020-07-07 16:00 ` Derrick Stolee
2020-07-07 16:45 ` Junio C Hamano
2020-07-07 16:49 ` Taylor Blau
2020-07-07 17:21 ` SZEDER Gábor
2020-07-07 18:12 ` Junio C Hamano
2020-07-10 21:13 ` SZEDER Gábor
2020-07-10 21:38 ` Junio C Hamano
2020-07-08 14:31 ` mr/bisect-in-c-2, was Re: What's cooking in git.git (Jul 2020, #01; Mon, 6) Johannes Schindelin
2020-07-08 15:43 ` Junio C Hamano
2020-07-08 23:11 ` Junio C Hamano [this message]
2020-07-09 9:20 ` Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqy2ntzjoi.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).