git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PUB]What's cooking in git.git (Aug 2015, #05; Fri, 28)

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Aug 31, 2015, 17:16 UTC
Message-ID
<vpq4mjf74zu.fsf@anie.imag.fr>
In-Reply-To
<xmqqmvx7xz45.fsf@gitster.mtv.corp.google.com>
Junio C Hamano <gitster@pobox.com> writes:
Show 31 quoted lines
> Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
>
>> Junio C Hamano <gitster@pobox.com> writes:
>>
>>> * ad/bisect-terms (2015-08-03) 4 commits
>>>  - bisect: allow setting any user-specified in 'git bisect start'
>>>  - bisect: add 'git bisect terms' to view the current terms
>>>  - bisect: add the terms old/new
>>>  - bisect: sanity check on terms
>>>
>>>  The use of 'good/bad' in "git bisect" made it confusing to use when
>>>  hunting for a state change that is not a regression (e.g. bugfix).
>>>  The command learned 'old/new' and then allows the end user to
>>>  say e.g. "bisect start --term-old=fast --term=new=slow" to find a
>>>  performance regression.
>>>
>>>  Michael's idea to make 'good/bad' more intelligent does have
>>>  certain attractiveness ($gname/272867), and makes some of the work
>>>  on this topic a moot point.
>>>
>>>  Will hold.
>>
>> This topic has been there for a while and unless I missed a discussion,
>> nothing happened. While I agree that Michael's idea is good and makes
>> this series less useful, I think this topic also makes sense.
>>
>> I'd be in favor of merging it.
>
> "Nothing happened" is never a good enough reason to argue for
> merging new stuff, but now you are starting a discussion here, let's
> see where it takes us to.  I am neutral myself at this moment.

Right, but my feeling after the previous discussion was that people were mostly in favor of merging the changes (i.e. allowing user-defined bisect terms), but we wanted to make sure we didn't get any objection on second thought, hence it was a good thing to have an extended cooking period.

To add arguments in favor of merging: even if we get the "auto swap good/bad", having user-defined terms can still help for situations where the change between states does not correspond to a situation where one state is 'good' and one is 'bad' eg. --term-old=red --term-new=blue.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: Junio C Hamano
Message 11 of 11 in “What's cooking in git.git (Aug 2015, #05; Fri, 28)”
  1. Junio C HamanoAug 28, 2015
  2. Eric SunshineAug 28, 2015
  3. Christian CouderAug 29, 2015
  4. Junio C HamanoAug 31, 2015
  5. David TurnerAug 31, 2015
  6. Junio C HamanoAug 31, 2015
  7. Christian CouderAug 31, 2015
  8. Matthieu MoyAug 31, 2015
  9. Christian CouderAug 31, 2015
  10. Junio C HamanoAug 31, 2015
  11. Matthieu MoyAug 31, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.