From: Jeff King <firstname.lastname@example.org>
To: Jeff Hostetler <email@example.com>
Cc: Git Mailing List <firstname.lastname@example.org>,
Junio C Hamano <email@example.com>,
Ben Peart <firstname.lastname@example.org>,
Jameson Miller <email@example.com>,
Derrick Stolee <firstname.lastname@example.org>
Subject: Re: Question about the ahead-behind computation and status
Date: Fri, 15 Dec 2017 05:08:35 -0500 [thread overview]
Message-ID: <20171215100835.GC3567@sigill.intra.peff.net> (raw)
On Thu, Dec 14, 2017 at 04:49:31PM -0500, Jeff Hostetler wrote:
> I don't want to jump into the graph algorithm at this time,
> but was wondering about adding a --no-ahead-behind flag (or
> something similar or a config setting) that would disable
> the a/b computation during status.
> For status V2 output, we could omit the "# branch.ab x y"
> line. For normal status output, change the prose a/b
> message to say something like "are [not] up to date".
Is it actually "status --porcelain=v2" that you care about here? Or is
it normal "git status"?
Do you care about seeing the branch at all? I.e., would "--no-branch" be
a viable option (though I notice it seems to be a silent noop with the
long-form, which should probably be fixed).
If you really do want to see all branch details but just skip the
ahead/behind, then yeah, I'd agree that adding an option to do so makes
sense. Is "status" the only command that needs it? I think we do it
unconditionally with "git checkout", too.
> [*] Sadly, the local repo was only about 20 days out of
> date (including the Thanksgiving holidays)....
Taking 20 seconds to traverse 20 days worth of history sounds pretty
awful. How many commits is it?
next prev parent reply other threads:[~2017-12-15 10:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 21:49 Question about the ahead-behind computation and status Jeff Hostetler
2017-12-15 10:08 ` Jeff King [this message]
2017-12-15 15:08 ` Jeff Hostetler
2017-12-15 15:43 ` Derrick Stolee
2017-12-15 18:30 ` Junio C Hamano
2017-12-15 19:40 ` Derrick Stolee
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: 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 \
* 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).