Re: What's cooking in git.git (Feb 2018, #03; Wed, 21)

From: Jeff Hostetler <git@jeffhostetler.com>
Date: Feb 27, 2018, 13:49 UTC
Message-ID: <29bd960d-80e4-8bd6-c8f2-aa2860de183b@jeffhostetler.com>
In-Reply-To: <xmqq1shdyidz.fsf@gitster-ct.c.googlers.com>

On 2/21/2018 7:31 PM, Junio C Hamano wrote:

Show 12 quoted lines

> 
> * jh/status-no-ahead-behind (2018-01-24) 4 commits
>   - status: support --no-ahead-behind in long format
>   - status: update short status to respect --no-ahead-behind
>   - status: add --[no-]ahead-behind to status and commit for V2 format.
>   - stat_tracking_info: return +1 when branches not equal
> 
>   "git status" can spend a lot of cycles to compute the relation
>   between the current branch and its upstream, which can now be
>   disabled with "--no-ahead-behind" option.
> 
>   At v5; is this ready for 'next'?

yes, i believe so.

thanks jeff