From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.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: Wed, 12 Feb 2025 08:58:23 -0800 [thread overview]
Message-ID: <xmqqh64zumkw.fsf@gitster.g> (raw)
In-Reply-To: <5b605c3e-ef6a-433a-9637-1e8f277dfde9@gmail.com> (Phillip Wood's message of "Wed, 12 Feb 2025 14:26:52 +0000")
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.
next prev parent reply other threads:[~2025-02-12 16:58 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 [this message]
2025-02-13 9:43 ` Phillip Wood
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=xmqqh64zumkw.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=alexhenrie24@gmail.com \
--cc=git@vger.kernel.org \
--cc=intelfx@intelfx.name \
--cc=newren@gmail.com \
--cc=phillip.wood123@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.