Re: [PATCH v25 2/2] status: show comparison with push remote tracking branch

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 15, 2026, 13:38 UTC
Message-ID: <xmqq5x93dmhf.fsf@gitster.g>
In-Reply-To: <0037e6b9-e57d-4cd3-b156-c8cbf439347a@gmail.com>

Phillip Wood <phillip.wood123@gmail.com> writes:

> So as well as configuring whether we show the comparison the push branch 
> it would be nice to be able to configure a simpler output as well. That 
> does not need to be part of this series but perhaps we should design the 
> configuration to be extendable.

So, there are orthogonal axes that might benefit from configurabiliity.

What other branch to compare (e.g., @{upstream}, @{push}, something else?) and how detailed comparison we want (e.g., only tell me when we are ahead with just a single bit, give me ahead/behind count, only tell me when we are behind with just a single bit, etc.).

There may be other interesting axes people may be able to come up with in the future. We do not have to be exhaustive on values on all axes on the first day, but it would be nice to have a fairly complete coverage of what axes matter to users, and it is a great suggestion that the level of details can be one. Thanks.