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

[PATCH 3/4] bisect: simplify the add of new bisect terms

From
Antoine Delaite <antoine.delaite@ensimag.grenoble-inp.fr>
Date
Jun 10, 2015, 07:09 UTC
Message-ID
<1975406107.331328.1433920182747.JavaMail.zimbra@ensimag.grenoble-inp.fr>
In-Reply-To
<1183699596.323718.1433875699237.JavaMail.zimbra@ensimag.grenoble-inp.fr>
Hi, 

Thanks for the review ! (sorry if you received this twice)

Christian Couder <christian.couder@gmail.com> wrote : 
Show 26 quoted lines
>>> + name_bad = "bad"; 
>>> + name_good = "good"; 
>>> + } else { 
>>> + strbuf_getline(&str, fp, '\n'); 
>>> + name_bad = strbuf_detach(&str, NULL); 
>>> + strbuf_getline(&str, fp, '\n'); 
>>> + name_good = strbuf_detach(&str, NULL); 
>>> + } 
>> 
>> I would have kept just 
>> 
>> name_bad = "bad"; 
>> name_good = "good"; 
>> 
>> in this patch, and introduce BISECT_TERMS in a separate one. 
> 
>Yeah I agree that it is more logical to have first a patch that does 
>on bisect.c the same thing as patch 2 does on git-bisect.sh. 
> 
>For example the patch series could be for now: 
> 
>1) bisect: typo fix 
>2) bisect: replace hardcoded "bad|good" with variables 
>3) git-bisect: replace hardcoded "bad|good" with variables 
>4) bisect: simplify adding new terms 
>5) bisect: add old/new terms 

For now we will keep name_bad and name_good as variables. About the patch series shouldn't I squash the commit 2) and 3) into one?

Message 1 of 1 in “bisect: simplify the add of new bisect terms”
  1. 3/4 bisect: simplify the add of new bisect termsAntoine Delaite, Jun 10, 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.