git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phillip Wood <phillip.wood123@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Ivan Shapovalov <intelfx@intelfx.name>,
	phillip.wood@dunelm.org.uk, git@vger.kernel.org,
	Elijah Newren <newren@gmail.com>,
	Derrick Stolee <stolee@gmail.com>,
	Alex Henrie <alexhenrie24@gmail.com>
Subject: Re: [PATCH] rebase: add `--update-refs=interactive`
Date: Thu, 13 Feb 2025 09:43:20 +0000	[thread overview]
Message-ID: <27f4e010-e2fb-4e80-b64d-3843c9fc3f55@gmail.com> (raw)
In-Reply-To: <xmqqh64zumkw.fsf@gitster.g>

On 12/02/2025 16:58, Junio C Hamano wrote:
> 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

  reply	other threads:[~2025-02-13  9:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 19:16 [PATCH] rebase: add `--update-refs=interactive` Ivan Shapovalov
2025-02-10 20:22 ` D. Ben Knoble
2025-02-11 11:33   ` Ivan Shapovalov
2025-02-11 16:50     ` Junio C Hamano
2025-02-11 17:36       ` Ivan Shapovalov
2025-02-11 19:28     ` D. Ben Knoble
2025-02-11 19:29       ` D. Ben Knoble
2025-02-11 14:36 ` Phillip Wood
2025-02-11 18:11   ` Ivan Shapovalov
2025-02-12 14:26     ` Phillip Wood
2025-02-12 16:58       ` Junio C Hamano
2025-02-13  9:43         ` Phillip Wood [this message]
2025-02-12 17:18       ` Ivan Shapovalov
2025-02-13  9:43         ` phillip.wood123
2025-02-13 12:04           ` Ivan Shapovalov
2025-02-19 14:52             ` phillip.wood123

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=27f4e010-e2fb-4e80-b64d-3843c9fc3f55@gmail.com \
    --to=phillip.wood123@gmail.com \
    --cc=alexhenrie24@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=intelfx@intelfx.name \
    --cc=newren@gmail.com \
    --cc=phillip.wood@dunelm.org.uk \
    --cc=stolee@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).