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

[PATCH 0/4] code clean-up for rerere

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 24, 2023, 20:54 UTC
Message-ID
<20230824205456.1231371-1-gitster@pobox.com>

These are to clean up some odd code and in-code comment that invited "Huh?" while I was reviewing the code paths involved in "git rerere" recently. None of them is intended to change any behaviour.

Junio C Hamano (4):
  rerere: simplify check_one_conflict() helper function
  rerere: fix comment on handle_file() helper
  rerere: try_merge() should use LL_MERGE_ERROR when it means an error
  rerere: modernize use of empty strbuf
 rerere.c | 46 +++++++++++++++++++---------------------------
 1 file changed, 19 insertions(+), 27 deletions(-)
-- 
2.42.0-29-gcd9da15a85
Next: Junio C Hamano
Message 1 of 5 in “code clean-up for rerere”
  1. 0/4 code clean-up for rerereJunio C Hamano, Aug 24, 2023
  2. 3/4 rerere: try_merge() should use LL_MERGE_ERROR when it means an errorJunio C Hamano, Aug 24, 2023
  3. 1/4 rerere: simplify check_one_conflict() helper functionJunio C Hamano, Aug 24, 2023
  4. 4/4 rerere: modernize use of empty strbufJunio C Hamano, Aug 24, 2023
  5. 2/4 rerere: fix comment on handle_file() helperJunio C Hamano, Aug 24, 2023

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.