From: Jeff Hostetler <git@jeffhostetler.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: Derrick Stolee <stolee@gmail.com>
Subject: Re: What's cooking in git.git (Jan 2018, #03; Tue, 23)
Date: Wed, 24 Jan 2018 10:26:57 -0500 [thread overview]
Message-ID: <d154319e-bb9e-b300-7c37-27b1dcd2a2ce@jeffhostetler.com> (raw)
In-Reply-To: <xmqqefmgfbcx.fsf@gitster.mtv.corp.google.com>
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
next prev parent reply other threads:[~2018-01-24 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 22:39 What's cooking in git.git (Jan 2018, #03; Tue, 23) Junio C Hamano
2018-01-24 15:26 ` Jeff Hostetler [this message]
2018-01-24 22:37 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d154319e-bb9e-b300-7c37-27b1dcd2a2ce@jeffhostetler.com \
--to=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=stolee@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).