From: Michal Vyskocil <mvyskocil@suse.cz>
To: git@vger.kernel.org
Subject: Re: RFC: reverse bisect
Date: Fri, 30 Sep 2011 10:29:14 +0200 [thread overview]
Message-ID: <20110930082914.GD27152@zelva.suse.cz> (raw)
In-Reply-To: <4E849C5B.7050201@kdbg.org>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
On Thu, Sep 29, 2011 at 06:27:07PM +0200, Johannes Sixt wrote:
> Am 29.09.2011 16:20, schrieb Michal Vyskocil:
> > git bisect start --reverse HEAD~999 HEAD
>
> With the regular meaning of the start subcommand, the revs given are
> ordered: bad good good...
>
> With the reversed meaning, this would have to become: good bad bad...
>
> This would have to be mentioned clearly in the documentation.
>
> > git bisect good/bad/skip/run
>
> Last time this came up on the list I suggested to add the following
> commands:
>
> git bisect regression # a synonym for git bisect start
> git bisect improvement # your --reverse
Good point! As you mentioned, the --switch already reverse the meanings
of arguments as you mentioned. Using a new command will be less
confusing for users.
Michal Vyskocil
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-09-30 8:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 14:20 RFC: reverse bisect Michal Vyskocil
2011-09-29 14:42 ` Sverre Rabbelier
2011-09-29 16:27 ` Johannes Sixt
2011-09-30 4:09 ` Jeff King
2011-09-30 5:31 ` Frans Klaver
2011-09-30 8:29 ` Michal Vyskocil [this message]
2011-09-30 11:42 ` [RFC/PATCH]: reverse bisect v 2.0 Michal Vyskocil
2011-09-30 18:13 ` Junio C Hamano
2011-10-03 10:41 ` Jeff King
2011-10-03 17:00 ` Junio C Hamano
2011-10-04 10:30 ` Jeff King
2011-10-04 15:22 ` Junio C Hamano
2011-10-04 22:34 ` Christian Couder
2011-10-04 23:27 ` Junio C Hamano
2011-10-07 1:57 ` Andrew Ardill
2011-10-12 4:57 ` Junio C Hamano
2011-10-12 20:14 ` Jeff King
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=20110930082914.GD27152@zelva.suse.cz \
--to=mvyskocil@suse.cz \
--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 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.