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

Re: [PATCH] rebase: add `--update-refs=interactive`

From
PWPhillip Wood <phillip.wood123@gmail.com>
Date
Feb 13, 2025, 09:43 UTC
Message-ID
<27f4e010-e2fb-4e80-b64d-3843c9fc3f55@gmail.com>
In-Reply-To
<xmqqh64zumkw.fsf@gitster.g>
On 12/02/2025 16:58, Junio C Hamano wrote:
Show 14 quoted lines
> Phillip Wood <phillip.wood123@gmail.com> writes:
> 
>> Maintaining multiple versions of the same branch sounds like a lot of
>> work - whats the advantage over merging a single branch into each
>> release?
> 
> Making a single branch that would merge to each release track
> cleanly, with preparing and maintaining semantic fixes necessary for
> each track, is probably equally a lot of work, if not more.  I try
> to do that for this project only because I am a perfectionist for
> these things (and do so for fun), but I can understand if many
> others (a pragmatist in me included) consider it not worth the
> effort.  After all, it stops mattering once the branch finally gets
> merged.

Thanks for that insight, I'd assumed the benefits of having a single source of truth for each branch outweighed the costs but it seems that is not necessarily the case.

Best Wishes
Phillip
Previous: Junio C HamanoNext: Ivan Shapovalov
Message 12 of 16 in “rebase: add `--update-refs=interactive`”
  1. rebase: add `--update-refs=interactive`Ivan Shapovalov, Feb 10, 2025
  2. D. Ben KnobleFeb 10, 2025
  3. Ivan ShapovalovFeb 11, 2025
  4. Junio C HamanoFeb 11, 2025
  5. Ivan ShapovalovFeb 11, 2025
  6. D. Ben KnobleFeb 11, 2025
  7. D. Ben KnobleFeb 11, 2025
  8. Phillip WoodFeb 11, 2025
  9. Ivan ShapovalovFeb 11, 2025
  10. Phillip WoodFeb 12, 2025
  11. Junio C HamanoFeb 12, 2025
  12. Phillip WoodFeb 13, 2025
  13. Ivan ShapovalovFeb 12, 2025
  14. phillip.wood123@gmail.comFeb 13, 2025
  15. Ivan ShapovalovFeb 13, 2025
  16. phillip.wood123@gmail.comFeb 19, 2025

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.