mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Derrick Stolee via GitGitGadget" <>
Cc: git@jeffhostetler, Junio C Hamano <>
Subject: [PATCH 0/3] git-status: create config for ahead/behind calculation
Date: Tue, 18 Jun 2019 13:21:25 -0700 (PDT)	[thread overview]
Message-ID: <> (raw)

The git status builtin includes a calculation for how far the local ref is
ahead or behind the remote tracking branch. This check can be expensive, so
we already have a --[no-]ahead-behind command-line option.

This series adds two bits of functionality to the feature:

 1. Add a new status.aheadBehind config setting.
 2. Add a new advice.statusAheadBehind config setting associated with a
    warning that suggests status.aheadBehind when the calculation takes a
    long time.

We have been running with these commits in microsoft/git for a while now.
The only change I made in adapting Jeff's commits was to add the advice
config documentation.

The status.aheadBehind config setting is a candidate to be added to the
proposed "large repo" meta-config setting previously discussed [1]. I'm
putting this out for independent review as it is much smaller compared to
the potential of that series.

Thanks, -Stolee


Jeff Hostetler (3):
  status: add status.aheadbehind setting
  status: warn when a/b calculation takes too long
  status: ignore status.aheadbehind in porcelain formats

 Documentation/config/advice.txt |  6 ++++++
 Documentation/config/status.txt |  5 +++++
 advice.c                        |  2 ++
 advice.h                        |  1 +
 builtin/commit.c                | 19 ++++++++++++++++++-
 t/        | 31 +++++++++++++++++++++++++++++++
 t/         |  8 ++++++++
 wt-status.c                     | 17 +++++++++++++++++
 8 files changed, 88 insertions(+), 1 deletion(-)

base-commit: b697d92f56511e804b8ba20ccbe7bdc85dc66810
Fetch-It-Via: git fetch pr-272/derrickstolee/status-ahead-behind-v1

             reply	other threads:[~2019-06-18 20:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18 20:21 Derrick Stolee via GitGitGadget [this message]
2019-06-18 20:21 ` [PATCH 1/3] status: add status.aheadbehind setting Jeff Hostetler via GitGitGadget
2019-06-21 16:33   ` Junio C Hamano
2019-06-26 20:02     ` Jeff Hostetler
2019-06-29 17:30   ` SZEDER Gábor
2019-06-18 20:21 ` [PATCH 2/3] status: warn when a/b calculation takes too long Jeff Hostetler via GitGitGadget
2019-06-18 20:21 ` [PATCH 3/3] status: ignore status.aheadbehind in porcelain formats Jeff Hostetler via GitGitGadget

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \
    --cc=git@jeffhostetler \ \ \

* 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

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).