From: Stephan Beyer <s-beyer@gmx.net>
To: Junio C Hamano <gitster@pobox.com>,
Christian Couder <christian.couder@gmail.com>
Cc: "Robert P. J. Day" <rpjday@crashcourse.ca>,
Git Mailing list <git@vger.kernel.org>,
Pranit Bauva <pranit.bauva@gmail.com>
Subject: Re: should "git bisect" support "git bisect next?"
Date: Sun, 12 Nov 2017 21:08:35 +0100 [thread overview]
Message-ID: <cc11ab35-a219-8cab-313e-f716723409e4@gmx.net> (raw)
In-Reply-To: <xmqq4lq0ev8g.fsf@gitster.mtv.corp.google.com>
Hi,
On 11/11/2017 03:38 PM, Junio C Hamano wrote:
> Christian Couder <christian.couder@gmail.com> writes:
>
>> On Sat, Nov 11, 2017 at 12:42 PM, Robert P. J. Day
>> <rpjday@crashcourse.ca> wrote:
>>>
>>> the man page for "git bisect" makes no mention of "git bisect next",
>>> but the script git-bisect.sh does:
>>
>> Yeah the following patch was related:
>>
>> https://public-inbox.org/git/1460294354-7031-2-git-send-email-s-beyer@gmx.net/
>>
>> You might want to discuss with Stephan (cc'ed).
>
> Thanks for saving me time to explain why 'next' is still a very
> important command but the end users do not actually need to be
> strongly aware of it, because most commands automatically invokes it
> as their final step due to the importance of what it does ;-)
I will nonetheless re-roll the patch (that Christian linked to)
after Pranit's bisect part II series is in good shape. I think the
documentation change in the patch shows why the user should be aware of
it (although not strongly).
Best
Stephan
prev parent reply other threads:[~2017-11-12 20:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-11 11:42 should "git bisect" support "git bisect next?" Robert P. J. Day
2017-11-11 14:07 ` Christian Couder
2017-11-11 14:38 ` Junio C Hamano
2017-11-11 19:46 ` Theodore Ts'o
2017-11-12 1:43 ` Junio C Hamano
2017-11-12 14:21 ` Christian Couder
2017-11-12 18:42 ` Theodore Ts'o
2017-11-13 1:40 ` Junio C Hamano
2017-11-12 9:17 ` Robert P. J. Day
2017-11-12 9:56 ` Junio C Hamano
2017-11-12 20:08 ` Stephan Beyer [this message]
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=cc11ab35-a219-8cab-313e-f716723409e4@gmx.net \
--to=s-beyer@gmx.net \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pranit.bauva@gmail.com \
--cc=rpjday@crashcourse.ca \
/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).