From: "Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: git@jeffhostetler, Junio C Hamano <gitster@pobox.com>
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: <pull.272.git.gitgitgadget@gmail.com> (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
[1] https://public-inbox.org/git/pull.254.git.gitgitgadget@gmail.com/
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/t6040-tracking-info.sh | 31 +++++++++++++++++++++++++++++++
t/t7064-wtstatus-pv2.sh | 8 ++++++++
wt-status.c | 17 +++++++++++++++++
8 files changed, 88 insertions(+), 1 deletion(-)
base-commit: b697d92f56511e804b8ba20ccbe7bdc85dc66810
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-272%2Fderrickstolee%2Fstatus-ahead-behind-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-272/derrickstolee/status-ahead-behind-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/272
--
gitgitgadget
next 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pull.272.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@jeffhostetler \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.