From: Johannes Sixt <j6t@kdbg.org>
To: Christian Couder <christian.couder@gmail.com>
Cc: "Aaron S. Meurer" <asmeurer@gmail.com>,
git@vger.kernel.org, "SZEDER Gábor" <szeder@ira.uka.de>,
"Jonathan Nieder" <jrnieder@gmail.com>
Subject: Re: git bisect problems/ideas
Date: Fri, 21 Jan 2011 23:04:35 +0100 [thread overview]
Message-ID: <201101212304.36741.j6t@kdbg.org> (raw)
In-Reply-To: <AANLkTikG6Ft3Y922Aaakf28cnYs26PcRHoq9GSNj04mu@mail.gmail.com>
On Freitag, 21. Januar 2011, Christian Couder wrote:
> On Wed, Jan 19, 2011 at 8:44 PM, Aaron S. Meurer <asmeurer@gmail.com> wrote:
> > If no, I think --reverse is actually a suitable fix.
>
> Yeah, but I think that what Dscho started was probably better. The
> problem is just that it is not so simple to implement and no one yet
> has been interested enough or took enough time to finish it.
Let me throw in an idea:
Add two new sub-commands:
* 'git bisect regression': this is a synonym for 'git bisect start'.
* 'git bisect improvement': this also starts a bisection, but subsequently the
operation of 'git bisect good' and 'git bisect bad' is reversed.
-- Hannes
next prev parent reply other threads:[~2011-01-21 22:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-15 7:33 git bisect problems/ideas Aaron S. Meurer
2011-01-17 9:38 ` Christian Couder
2011-01-17 11:51 ` Jonathan Nieder
2011-01-17 13:38 ` SZEDER Gábor
2011-01-17 20:55 ` Jonathan Nieder
2011-01-18 9:05 ` Christian Couder
2011-01-17 18:27 ` Aaron S. Meurer
2011-01-17 18:23 ` Aaron S. Meurer
2011-01-18 9:04 ` Christian Couder
2011-01-18 18:34 ` Junio C Hamano
2011-01-19 13:15 ` Christian Couder
2011-01-19 19:15 ` Aaron S. Meurer
2011-01-19 19:29 ` Junio C Hamano
2011-01-19 19:44 ` Aaron S. Meurer
2011-01-21 13:18 ` Christian Couder
2011-01-21 22:04 ` Johannes Sixt [this message]
2011-01-22 14:52 ` Jakub Narebski
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=201101212304.36741.j6t@kdbg.org \
--to=j6t@kdbg.org \
--cc=asmeurer@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=szeder@ira.uka.de \
/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.