From: Jacopo Notarstefano <jacopo.notarstefano@gmail.com>
Date: Fri, 28 Feb 2014 09:00:53 GMT
Subject: Re: An idea for "git bisect" and a GSoC enquiry
Message-ID: <CAL0uuq23E+2gX14yAyeGFPySV0qTF8=-642PHqmogTDwz7F8Sg@mail.gmail.com>
In-Reply-To: <xmqqzjld3ate.fsf@gitster.dls.corp.google.com>

Mh. Haven't thought of that. I have no experience with TK, so I'm
having trouble digging up where the "good" and "bad" labels in the GUI
are generated.

I guess that a solution might involve writing a temporary file in
$GIT_DIR called something like BISECT_LABELS in which the chosen
labels are listed and reused across all tools that require them.

(Sorry for sending this email twice, I thought I had sent it to the
list as well!)

On Wed, Feb 26, 2014 at 8:58 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Jacopo Notarstefano <jacopo.notarstefano@gmail.com> writes:
>
>> Does this make sense? Did I overlook some details?
>
> How does this solve the labels shown in "git bisect visualize"?
>