git/list[1] front-page[2] threads[3] people[4] search[5] about
wed 2026-10-07 18:10 UTC

Re: [PATCH v2 1/5] replay: remove dead code and rearrange

From
Kristoffer Haugsbakk <code@khaugsbakk.name>
Date
Jan 2, 2026, 09:51 UTC
Message-ID
<3dfe9f23-cf54-4162-a90d-69ef9788d6b9@app.fastmail.com>
In-Reply-To
<CABPp-BEJV1XG62_hn_OiZ9q9S3jsyTP0VdOEzS4pME2rrkKFrg@mail.gmail.com>
On Tue, Dec 30, 2025, at 23:50, Elijah Newren wrote:
Show 21 quoted lines
> On Tue, Dec 30, 2025 at 7:03 AM <kristofferhaugsbakk@fastmail.com> wrote:
>>[snip]
>> -static void determine_replay_mode(struct repository *repo,
>> -                                 struct rev_cmdline_info *cmd_info,
>> -                                 const char *onto_name,
>> -                                 char **advance_name,
>> -                                 struct commit **onto,
>> -                                 struct strset **update_refs)
>> +static void populate_for_onto_or_advance_mode(struct repository *repo,
>> +                                             struct rev_cmdline_info *cmd_info,
>> +                                             const char *onto_name,
>> +                                             char **advance_name,
>> +                                             struct commit **onto,
>> +                                             struct strset **update_refs)
>
> Renaming makes sense, but the new name is quite the mouthful, and it
> feels slightly odd because "onto" is both a command line flag and a
> variable -- and the variable value is used regardless of which command
> line flag is used.  Since the variable is used either way, there's a
> risk someone might be confused by this function name.  Maybe just
> setup_replay_mode() ?  Or maybe others have other suggestions?
Yeah, it is a mouthful.
I can use `set_up_replay_mode`.
>>[snip]
>
> Looks fine otherwise.
Thanks for reviewing this round!
Previous: Junio C HamanoNext: Kristoffer Haugsbakk
Message 25 of 35 in “replay: die descriptively when invalid commit-ish”
  1. 0/2 replay: die descriptively when invalid commit-ishkristofferhaugsbakk@fastmail.com, Dec 22, 2025
  2. 1/2 replay: die descriptively when invalid commit-ishkristofferhaugsbakk@fastmail.com, Dec 22, 2025
  3. 2/2 t3650: add more regression tests for failure conditionskristofferhaugsbakk@fastmail.com, Dec 22, 2025
  4. Junio C HamanoDec 23, 2025
  5. Junio C HamanoDec 23, 2025
  6. Phillip WoodDec 23, 2025
  7. Phillip WoodDec 23, 2025
  8. Junio C HamanoDec 23, 2025
  9. Elijah NewrenDec 24, 2025
  10. Kristoffer HaugsbakkDec 30, 2025
  11. Kristoffer HaugsbakkDec 30, 2025
  12. Kristoffer HaugsbakkDec 30, 2025
  13. Kristoffer HaugsbakkDec 30, 2025
  14. 0/5 replay: die descriptively when invalid commit-ishkristofferhaugsbakk@fastmail.com, Dec 30, 2025
  15. 1/5 replay: remove dead code and rearrangekristofferhaugsbakk@fastmail.com, Dec 30, 2025
  16. 2/5 replay: find *onto only after testing for ref namekristofferhaugsbakk@fastmail.com, Dec 30, 2025
  17. 3/5 replay: die descriptively when invalid commit-ish is givenkristofferhaugsbakk@fastmail.com, Dec 30, 2025
  18. 4/5 replay: die if we cannot parse objectkristofferhaugsbakk@fastmail.com, Dec 30, 2025
  19. 5/5 t3650: add more regression tests for failure conditionskristofferhaugsbakk@fastmail.com, Dec 30, 2025
  20. Elijah NewrenDec 30, 2025
  21. Elijah NewrenDec 30, 2025
  22. Elijah NewrenDec 30, 2025
  23. Elijah NewrenDec 30, 2025
  24. Junio C HamanoDec 30, 2025
  25. Kristoffer HaugsbakkJan 2, 2026
  26. Kristoffer HaugsbakkJan 2, 2026
  27. 0/6 replay: die descriptively when invalid commit-ishkristofferhaugsbakk@fastmail.com, Jan 5, 2026
  28. 1/6 replay: remove dead code and rearrangekristofferhaugsbakk@fastmail.com, Jan 5, 2026
  29. 2/6 replay: find *onto only after testing for ref namekristofferhaugsbakk@fastmail.com, Jan 5, 2026
  30. 3/6 replay: die descriptively when invalid commit-ish is givenkristofferhaugsbakk@fastmail.com, Jan 5, 2026
  31. 4/6 replay: improve code comment and die messagekristofferhaugsbakk@fastmail.com, Jan 5, 2026
  32. 5/6 replay: die if we cannot parse objectkristofferhaugsbakk@fastmail.com, Jan 5, 2026
  33. 6/6 t3650: add more regression tests for failure conditionskristofferhaugsbakk@fastmail.com, Jan 5, 2026
  34. Elijah NewrenJan 6, 2026
  35. Junio C HamanoJan 7, 2026

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.