From: Junio C Hamano <gitster@pobox.com>
To: "Hugo Locurcio via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Hugo Locurcio <hugo.locurcio@hugo.pro>
Subject: Re: [PATCH] bisect: swap command-line options in documentation
Date: Fri, 28 Aug 2020 14:05:28 -0700 [thread overview]
Message-ID: <xmqqbliuo50n.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <pull.711.git.1598628679830.gitgitgadget@gmail.com> (Hugo Locurcio via GitGitGadget's message of "Fri, 28 Aug 2020 15:31:19 +0000")
"Hugo Locurcio via GitGitGadget" <gitgitgadget@gmail.com> writes:
> + git bisect start [--term-{new,bad}=<term> --term-{old,good}=<term>]
> [--no-checkout] [--first-parent] [<bad> [<good>...]] [--] [<paths>...]
Yeah, matching the --term-{bad,good} and the actual arguments may
make it easier to see the correspondence between them. Good idea.
In the old days, back when there weren't "--term-*=<myword>", it was
much simpler. All people have to do was to remember that <bad> and
<good> are ordered alphabetically.
Will queue. Thanks.
prev parent reply other threads:[~2020-08-28 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 15:31 [PATCH] bisect: swap command-line options in documentation Hugo Locurcio via GitGitGadget
2020-08-28 21:05 ` Junio C Hamano [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqbliuo50n.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=hugo.locurcio@hugo.pro \
/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 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 NNTP newsgroup(s).