Re: [PATCH v28 2/2] status: add status.compareBranches config for multiple branch comparisons
- From
D. Ben Knoble <ben.knoble@gmail.com>
- Date
- Feb 25, 2026, 17:04 UTC
- Message-ID
- <CALnO6CC5WE=K4sX+1NdNc+dV7KJWQvgdChoOfWWJyDQKH5uzJA@mail.gmail.com>
- In-Reply-To
- <20260225102228.95152-1-haraldnordgren@gmail.com>
On Wed, Feb 25, 2026 at 5:24 AM Harald Nordgren <haraldnordgren@gmail.com> wrote:
Show 15 quoted lines
>
> >> So what about this. We add a config option that takes a list of items to
> >> compare against. But it _only_ supports @{upstream} and @{push} for now,
> >> and interprets them as branch@{upstream} and branch@{push} (but probably
> >> done manually, not via dwim_ref). That limitation gets documented.
> >
> > Sounds like a good way forward.
>
> So if I do these changes, are we ready to merge then?
>
> I worked on this feature for 2 months, and then it got marked as stale
> instead of being merged. Will this time be different?
>
>
> HaraldTry not to be discouraged. It is not unusual for a series to undergo lengthy work and many revisions. It's part of what keeps Git working so well.
-- D. Ben Knoble