On 1/23/2018 5:39 PM, Junio C Hamano wrote:
[Stalled] * jh/status-no-ahead-behind (2018-01-04) 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 Expecting a reroll to finalize the topic.
I sent a V5 (1/9/2018) of this series that removed the config setting. It looks like your branch on GH only has the V4 version. WRT the reroll: There was a long discussion on a limited calculation (option (2)). While I appreciate how that would be nice to have (for some simple cases -- like my current feature branch relative to my upstream), I think that that is something we could add later if we want. (*) This patch gives a simple on/off. This has value by itself for certain situations. (*) To implement a limit would involve hacking the merge-base calculation which gets into graph shape questions that I don't think we want to get into. Several messages in the thread talk about some example shapes, but I don't think we have consensus on what we want here. (*) Later this week Stolee will be submitting a patch series that add a client-side commit graph cache. This allows fast calculations and includes generation numbers. I'd rather wait until we have this in and then see if we want/need the limited option. Thanks, Jeff