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

Re: [PATCH v2 0/2] bisect: status improvements when bisect is not fully fleshed out

From
Junio C Hamano <gitster@pobox.com>
Date
May 7, 2022, 18:25 UTC
Message-ID
<xmqqk0axgpxl.fsf@gitster.g>
In-Reply-To
<YnZQvuyeu/WZLhXH@chrisdown.name>
Chris Down <chris@chrisdown.name> writes:
Show 6 quoted lines
> Thanks Junio and Taylor for reviewing. I have the following action
> items for v3:
>
> # [1/3] bisect: lowercase "Bisect:" to "bisect:" prior to wider use
>
> - New patch

My preference actually were to leave this change out of the topic. That is, instead of using "status:" in newer messages, have them use the same "Bisecting:", so that all the "where we are in the bisect session?" messages from the command use that same prefix.

I also wonder if the existing "Bisecting:" messages should also be sent as comment to the log file, using the same bisect_log_printf() helper (with the v2 patches, they are still using printf() and sent only to the standard output).

But this, just like "status:" -> "Bisecting:" -> "bisecting:" you reacted to, is just "I wonder...", and is not a suggestion to make changes as part of this series. Something to think about for a possible follow-up after we complete this topic.

But I do not mind if you want to go the extra mile to do all of the above as part of the series. It would make the series to require more reviews, which is why I generally recommend against extending the scope of the (initial) topic too much and instead leave as much additional changes to follow-up series after the initial series is done.

Show 14 quoted lines
> # [2/3] bisect: output state before we are ready to compute bisection 
> - Fix multiline comment style in bisect.h
> - Zero-initialise bisect_state directly, don't use memset()
> - Pass the bisect state struct as an argument into bisect_print_status
> - Change from "status:" to "bisecting:"
>
> # [3/3] bisect: output bisect setup status in bisect log
>
> - Use strbuf in bisect_log_printf
> - Change `git bisect log' use an output file in tests instead of piping
>
> I'll wait a bit to see if there's any further feedback and then will send v3.
>
> Thanks!
Previous: Chris DownNext: Chris Down
Message 18 of 19 in “bisect: status improvements when bisect is not fully fleshed out”
  1. 0/2 bisect: status improvements when bisect is not fully fleshed outChris Down, May 6, 2022
  2. 1/2 bisect: output state before we are ready to compute bisectionChris Down, May 6, 2022
  3. Taylor BlauMay 6, 2022
  4. Chris DownMay 6, 2022
  5. Junio C HamanoMay 6, 2022
  6. Junio C HamanoMay 6, 2022
  7. 2/2 bisect: output bisect setup status in bisect logChris Down, May 6, 2022
  8. Taylor BlauMay 6, 2022
  9. Chris DownMay 6, 2022
  10. Taylor BlauMay 9, 2022
  11. Junio C HamanoMay 6, 2022
  12. Junio C HamanoMay 6, 2022
  13. Junio C HamanoMay 6, 2022
  14. Taylor BlauMay 9, 2022
  15. Junio C HamanoMay 9, 2022
  16. Taylor BlauMay 9, 2022
  17. Chris DownMay 7, 2022
  18. Junio C HamanoMay 7, 2022
  19. Chris DownMay 7, 2022

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.