Re: [PATCH v2 1/5] core.aheadbehind: add new config setting

On 4/3/2018 7:39 AM, Derrick Stolee wrote: On 4/3/2018 6:18 AM, Ævar Arnfjörð Bjarmason wrote: On Tue, Apr 03 2018, Lars Schneider wrote: What is the state of this series? I can't find it in git/git nor in git-for-windows/git. I think Stolee mentioned the config in his Git Merge talk [1] and

Re: [PATCH v2 1/5] core.aheadbehind: add new config setting

On 4/3/2018 6:18 AM, Ævar Arnfjörð Bjarmason wrote: On Tue, Apr 03 2018, Lars Schneider wrote: What is the state of this series? I can't find it in git/git nor in git-for-windows/git. I think Stolee mentioned the config in his Git Merge talk [1] and I was about to test it/roll it out :-) It's

Re: [PATCH v2 1/5] core.aheadbehind: add new config setting

On Tue, Apr 03 2018, Lars Schneider wrote: >> On 04 Jan 2018, at 20:26, Jeff King wrote: >> >> On Wed, Dec 27, 2017 at 09:41:30AM -0800, Junio C Hamano wrote: >> >>> Jeff King writes: >>> I, too, had a funny feeling about calling this "core". But I didn't

Re: [PATCH v2 1/5] core.aheadbehind: add new config setting

> On 04 Jan 2018, at 20:26, Jeff King wrote: > > On Wed, Dec 27, 2017 at 09:41:30AM -0800, Junio C Hamano wrote: > >> Jeff King writes: >> >>> I, too, had a funny feeling about calling this "core". But I didn't have >>> a better name, as I'm not sure what other

Re: [PATCH v2 1/5] core.aheadbehind: add new config setting

On Wed, Dec 27, 2017 at 09:41:30AM -0800, Junio C Hamano wrote: > Jeff King writes: > > > I, too, had a funny feeling about calling this "core". But I didn't have > > a better name, as I'm not sure what other place we have for config > > options that cross many command

Re: [PATCH v2 1/5] core.aheadbehind: add new config setting

Hi, Jeff Hostetler wrote: > On 12/21/2017 3:43 PM, Jonathan Nieder wrote: >> I also wonder if there's a way to achieve the same benefit without >> having it be configurable. E.g. if a branch is way behind, couldn't >> we terminate the walk early to get the same bounded cost per branch >>

Re: [PATCH v2 1/5] core.aheadbehind: add new config setting

On 12/21/2017 3:43 PM, Jonathan Nieder wrote: Hi, Jeff Hostetler wrote: Created core.aheadbehind config setting and core_ahead_behind global variable. This value defaults to true. This value will be used in the next few commits as the default value for the --ahead-behind parameter.

Re: [PATCH v2 1/5] core.aheadbehind: add new config setting

Jeff King writes: > I, too, had a funny feeling about calling this "core". But I didn't have > a better name, as I'm not sure what other place we have for config > options that cross many command boundaries. "diff" and "status" don't > seem quite right to me. While you can argue

Re: [PATCH v2 1/5] core.aheadbehind: add new config setting

On Fri, Dec 22, 2017 at 10:21:23AM -0800, Junio C Hamano wrote: > >> +core.aheadbehind:: > >> + If true, tells commands like status and branch to print ahead and > >> + behind counts for the branch relative to its upstream branch. > >> + This computation may be very expensive when there is a

Re: [PATCH v2 1/5] core.aheadbehind: add new config setting

Jonathan Nieder writes: >> Created core.aheadbehind config setting and core_ahead_behind >> global variable. This value defaults to true. >> >> This value will be used in the next few commits as the default value >> for the --ahead-behind parameter. >> >> Signed-off-by: Jeff

Re: [PATCH v2 1/5] core.aheadbehind: add new config setting

Hi, Jeff Hostetler wrote: > Created core.aheadbehind config setting and core_ahead_behind > global variable. This value defaults to true. > > This value will be used in the next few commits as the default value > for the --ahead-behind parameter. > > Signed-off-by: Jeff Hostetler

Re: [PATCH v2 1/5] core.aheadbehind: add new config setting

Hi Jeff, On 21/12/2017 20:09, Jeff Hostetler wrote: > > diff --git a/Documentation/config.txt b/Documentation/config.txt > index 9593bfa..c78d6be 100644 > --- a/Documentation/config.txt > +++ b/Documentation/config.txt > @@ -895,6 +895,14 @@ core.abbrev:: > abbreviated object names to stay

[PATCH v2 1/5] core.aheadbehind: add new config setting

From: Jeff Hostetler Created core.aheadbehind config setting and core_ahead_behind global variable. This value defaults to true. This value will be used in the next few commits as the default value for the --ahead-behind parameter. Signed-off-by: Jeff Hostetler