From: Christian Couder <chriscool@tuxfamily.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH 1/2] rev-list: implement --bisect-all
Date: Mon, 8 Oct 2007 07:08:45 +0200 [thread overview]
Message-ID: <200710080708.46579.chriscool@tuxfamily.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0710080442420.4174@racer.site>
Hi Dscho,
Le lundi 8 octobre 2007, Johannes Schindelin a écrit :
> Hi,
>
> On Mon, 8 Oct 2007, Christian Couder wrote:
> > This option makes it possible to see all the potential bisection
> > points. The best ones are displayed first.
>
> Would it not be better to pass --bisect-vars a list of commits that we do
> not want to see? It could then mark them as "DUNNO", and still just
> output a single commit.
The problem is that after --bisect-vars we already pass some "good" and then
a bad commit. So we have to use another flag like --bisect-dunno and put
the dunno commits after this one.
Then there is the problem that revision.c reorders arguments and doesn't
know about "--bisect-*" flags. It is also used by a lot of other commands.
After struggling with revision.c for some time, I thought it would be
simpler and safer to come up first with something in shell.
Also please note that in some cases we cannot just output a single commit,
because we just dunno which commit is the first bad one.
> IMHO such a logic does not belong into a shell script, but into the C
> core.
There is a lot of the bisect logic implemented in git-bisect.sh already. The
long term plan is to rewrite it in C, but I am not sure that the "dunno"
logic should be the first part of it to be done in C.
Also I thought it was still fine to prototype new features in shell.
Best regards,
Christian.
next prev parent reply other threads:[~2007-10-08 5:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 3:34 [PATCH 1/2] rev-list: implement --bisect-all Christian Couder
2007-10-08 3:44 ` Johannes Schindelin
2007-10-08 5:08 ` Christian Couder [this message]
2007-10-08 5:08 ` Johannes Schindelin
2007-10-23 21:33 ` Junio C Hamano
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=200710080708.46579.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).