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

Re: What's cooking in git.git (Mar 2024, #05; Tue, 19)

From
Brian Lyles <brianmlyles@gmail.com>
Date
Mar 20, 2024, 15:15 UTC
Message-ID
<17be81eb83ff314d.70b1dd9aae081c6e.203dcd72f6563036@zivdesk>
In-Reply-To
<xmqqil1iqi37.fsf@gitster.g>
Hi Junio
Show 13 quoted lines
> * bl/cherry-pick-empty (2024-03-11) 7 commits
>  - cherry-pick: add `--empty` for more robust redundant commit handling
>  - cherry-pick: enforce `--keep-redundant-commits` incompatibility
>  - sequencer: do not require `allow_empty` for redundant commit options
>  - sequencer: treat error reading HEAD as unborn branch
>  - rebase: update `--empty=ask` to `--empty=stop`
>  - docs: clean up `--empty` formatting in git-rebase(1) and git-am (1)
>  - docs: address inaccurate `--empty` default with `--exec`
> 
>  "cherry-pick" told to keep redundant commits needs to be allowed to
>  create empty commits to do its job, but it required the user to
>  give the --allow-empty option, which was unnecessary.  Its UI has
>  also been tweaked a bit.

Note that the description here is a little out-of-date; we're no longer changing the relationship between --allow-empty and --keep-redundant-commits (and the user didn't have to manually supply --allow-empty previously). I'd summarize this as:

	Allow git-cherry-pick(1) to automatically drop redundant commits via
	a new `--empty` option, similar to the `--empty` options for
	git-rebase(1) and git-am(1). Includes a soft deprecation of
	`--keep-redundant-commits` as well as some related docs changes and
	sequencer code cleanup.
>  Comments?
>  source: <20240119060721.3734775-2-brianmlyles@gmail.com>

You can expect a v4 reroll tonight to address a few remaining comments. The only thing I haven't heard back on is this change [1] to the docs for the new `--empty` option, but I'm confident enough in my proposed alternative there that I'm comfortable rerolling even if I don't hear back today.

[1]: https://lore.kernel.org/git/CAHPHrSfiMbU55K2=8+hJZy1cMSRbYM77pCK8BdcAPHLvapHO_A@mail.gmail.com/
-- 
Thank you,
Brian Lyles
Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 15 in “What's cooking in git.git (Mar 2024, #05; Tue, 19)”
  1. Junio C HamanoMar 19, 2024
  2. Brian LylesMar 20, 2024
  3. Junio C HamanoMar 20, 2024
  4. Brian LylesMar 21, 2024
  5. Junio C HamanoMar 21, 2024
  6. Brian LylesMar 21, 2024
  7. Junio C HamanoMar 21, 2024
  8. Brian LylesMar 22, 2024
  9. Junio C HamanoMar 22, 2024
  10. Brian LylesMar 22, 2024
  11. Dragan SimicMar 22, 2024
  12. Max GautierMar 22, 2024
  13. Dragan SimicMar 22, 2024
  14. Junio C HamanoMar 22, 2024
  15. Dragan SimicMar 22, 2024

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.