From: Junio C Hamano <gitster@pobox.com>
To: Jacopo Notarstefano <jacopo.notarstefano@gmail.com>
Cc: Michael Haggerty <mhagger@alum.mit.edu>,
Git Mailing List <git@vger.kernel.org>,
Christian Couder <christian.couder@gmail.com>
Subject: Re: An idea for "git bisect" and a GSoC enquiry
Date: Wed, 12 Mar 2014 11:31:19 -0700 [thread overview]
Message-ID: <xmqqmwgvmfpk.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAL0uuq0LpQTQPeNVJgKGS2YLTT0gi_BM0wi02c0EP+kvBE4DyA@mail.gmail.com> (Jacopo Notarstefano's message of "Wed, 12 Mar 2014 02:32:39 +0100")
Jacopo Notarstefano <jacopo.notarstefano@gmail.com> writes:
> On Mon, Mar 3, 2014 at 7:34 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> I think you fundamentally cannot use two labels that are merely
>> "distinct" and bisect correctly. You need to know which ones
>> (i.e. good) are to be excluded and the other (i.e. bad) are to be
>> included when computing the "remaining to be tested" set of commits.
>
> Good point. Yes, this isn't viable.
But if you make them into --no-longer-X vs --still-X, then it will
be viable without us knowing what X means.
next prev parent reply other threads:[~2014-03-12 18:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 8:28 An idea for "git bisect" and a GSoC enquiry Jacopo Notarstefano
2014-02-26 19:58 ` Junio C Hamano
2014-02-28 9:00 ` Jacopo Notarstefano
2014-02-27 11:18 ` Michael Haggerty
2014-02-27 12:09 ` Matthieu Moy
2014-02-28 9:03 ` Jacopo Notarstefano
2014-02-28 18:31 ` Junio C Hamano
2014-03-01 11:31 ` Jacopo Notarstefano
2014-03-03 18:34 ` Junio C Hamano
2014-03-12 1:32 ` Jacopo Notarstefano
2014-03-12 18:31 ` Junio C Hamano [this message]
2014-03-13 17:19 ` Michael Haggerty
2014-03-13 18:47 ` Junio C Hamano
[not found] ` <CAL0uuq3TGb2wjaqNxwXYa++E5rjVoozox5mZbzTaE17OKtsVTg@mail.gmail.com>
[not found] ` <a8cf74b4-bae1-4511-a45e-d4ca90e3c3e1@email.android.com>
2014-02-28 9:07 ` Jacopo Notarstefano
2014-02-28 9:13 ` Jacopo Notarstefano
2014-02-27 14:47 ` Christian Couder
2014-02-27 22:46 ` Andrew Ardill
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=xmqqmwgvmfpk.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=jacopo.notarstefano@gmail.com \
--cc=mhagger@alum.mit.edu \
/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.