git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Jeff Hostetler <git@jeffhostetler.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, peff@peff.net,
	Jeff Hostetler <jeffhost@microsoft.com>
Subject: [PATCH v5 0/4] Add --no-ahead-behind to status
Date: Tue,  9 Jan 2018 18:50:14 +0000	[thread overview]
Message-ID: <20180109185018.69164-1-git@jeffhostetler.com> (raw)

From: Jeff Hostetler <jeffhost@microsoft.com>

This is version 5 of my patch series to avoid expensive ahead/behind
calculations in status.  This version completely removes the config
setting and is just the --[no-]ahead-behind command line argument.

Internally (inside MSFT) we have had further discussions in this
area and identified 2 somewhat independent needs:

[1] The first is to just be able to turn off the a/b calculation when
    the invoker does not need the result at all.

[2] The second is to greatly speed up or limit the a/b calculation on
    extremely large repositories.

    In earlier versions of this patch series, there were several
    discussions of a limited mode that would look for no more than n
    commits or milliseconds.  Also discussed were some problems that
    such limiting will have and it was decided to be not worth the effort.

    We have been discussing some ways to speed up the calculation on the
    client and have tentatively scheduled this shortly.  Hopefully, this
    will eliminate the performance problems and reduce the likelyhood
    that anyone would need to set a config setting to change the default
    behavior (in either porcelain or non-porcelain) formats.

So with that in mind, this version elimates the config setting so that
we have don't to carry forward a soon-to-be-obsolete setting.

All that remains in this version is the command line argument to turn
on/off the a/b calculation.

Jeff Hostetler (4):
  stat_tracking_info: return +1 when branches not equal
  status: add --[no-]ahead-behind to status and commit for V2 format.
  status: update short status to respect --no-ahead-behind
  status: support --no-ahead-behind in long format

 Documentation/git-status.txt |  5 ++++
 builtin/checkout.c           |  2 +-
 builtin/commit.c             |  7 +++++
 ref-filter.c                 |  8 +++---
 remote.c                     | 50 +++++++++++++++++++++++------------
 remote.h                     | 12 +++++++--
 t/t6040-tracking-info.sh     | 42 ++++++++++++++++++++++++++++++
 t/t7064-wtstatus-pv2.sh      | 62 ++++++++++++++++++++++++++++++++++++++++++++
 wt-status.c                  | 41 ++++++++++++++++++++---------
 wt-status.h                  |  2 ++
 10 files changed, 196 insertions(+), 35 deletions(-)

-- 
2.9.3


             reply	other threads:[~2018-01-09 18:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09 18:50 Jeff Hostetler [this message]
2018-01-09 18:50 ` [PATCH v5 1/4] stat_tracking_info: return +1 when branches not equal Jeff Hostetler
2018-01-09 18:50 ` [PATCH v5 2/4] status: add --[no-]ahead-behind to status and commit for V2 format Jeff Hostetler
2018-01-09 18:50 ` [PATCH v5 3/4] status: update short status to respect --no-ahead-behind Jeff Hostetler
2018-01-09 18:50 ` [PATCH v5 4/4] status: support --no-ahead-behind in long format Jeff Hostetler

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=20180109185018.69164-1-git@jeffhostetler.com \
    --to=git@jeffhostetler.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jeffhost@microsoft.com \
    --cc=peff@peff.net \
    /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 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).