From: Junio C Hamano <gitster@pobox.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org, Andreas Mohr <andi@lisas.de>
Subject: Re: [PATCH] git-bisect.txt: clarify that reset finishes bisect
Date: Sat, 09 Feb 2013 13:53:04 -0800 [thread overview]
Message-ID: <7v8v6xw3wf.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <5e23d4c420f150b700dd5100bffb38d32f874200.1360439176.git.git@drmicha.warpmail.net> (Michael J. Gruber's message of "Sat, 9 Feb 2013 20:47:13 +0100")
Michael J Gruber <git@drmicha.warpmail.net> writes:
> "reset" can be easily misunderstood as resetting a bisect session to its
> start without finishing it. Clarify that it actually finishes the bisect
> session.
>
> Reported-by: Andreas Mohr <andi@lisas.de>
> Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
> ---
> Documentation/git-bisect.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt
> index b4831bb..d50bd89 100644
> --- a/Documentation/git-bisect.txt
> +++ b/Documentation/git-bisect.txt
> @@ -83,7 +83,7 @@ Bisect reset
> ~~~~~~~~~~~~
>
> After a bisect session, to clean up the bisection state and return to
> -the original HEAD, issue the following command:
> +the original HEAD (i.e., to finish bisect), issue the following command:
Makes sense.
next prev parent reply other threads:[~2013-02-09 21:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-09 19:47 [PATCH] git-bisect.txt: clarify that reset finishes bisect Michael J Gruber
2013-02-09 21:53 ` Junio C Hamano [this message]
2013-02-09 23:24 ` Andreas Mohr
2013-02-09 23:35 ` Junio C Hamano
2013-02-10 0:23 ` Andreas Mohr
2013-02-10 1:49 ` Jonathan Nieder
2013-02-11 8:04 ` Michael J Gruber
2013-02-11 8:35 ` [PATCHv2] git-bisect.txt: clarify that reset quits bisect Michael J Gruber
2013-02-11 8:39 ` Jonathan Nieder
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=7v8v6xw3wf.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=andi@lisas.de \
--cc=git@drmicha.warpmail.net \
--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.
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).