Re: [PATCH v11 8/8] builtin/history: implement "reword" subcommand
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jan 18, 2026, 17:50 UTC
- Message-ID
- <87ms2a3j4l.fsf@gitster.g>
- In-Reply-To
- <CABPp-BHkNLdH4C7U4sFoVhrsSPH8KAaDtOdLEQGyajmXZz9hVg@mail.gmail.com>
Elijah Newren <newren@gmail.com> writes:
Show 6 quoted lines
> ... that they don't want to undo and lose. It feels like a > hard recovery story. In contrast, we can consider the case of the > default being to update all branches for a user who doesn't want it. > If that user finds that other local branches were also rebased and > they didn't want them to be, they just go reset that branch or > branches from the reflog, which is pretty easy.
Very nicely put. I originally thought that the "reflog is your friend" argument would apply in both direction, but leaving the tips of some branches behind while rewriting the tips of some other branches, that can reach the tips of these left-bhind branches, would mean we have no other commit to go back to.
Thanks.