git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 1/4] status: add --no-ahead-behind to porcelain V2

From
Jeff King <peff@peff.net>
Date
Dec 20, 2017, 16:07 UTC
Message-ID
<20171220160731.GA31149@sigill.intra.peff.net>
In-Reply-To
<20171220144245.39401-2-git@jeffhostetler.com>
On Wed, Dec 20, 2017 at 02:42:42PM +0000, Jeff Hostetler wrote:
Show 15 quoted lines
> diff --git a/Documentation/git-status.txt b/Documentation/git-status.txt
> index 9f3a78a..6ce8cf8 100644
> --- a/Documentation/git-status.txt
> +++ b/Documentation/git-status.txt
> @@ -111,6 +111,13 @@ configuration variable documented in linkgit:git-config[1].
>  	without options are equivalent to 'always' and 'never'
>  	respectively.
>  
> +--no-ahead-behind::
> +	Do not compute ahead/behind counts for the current branch relative
> +	to the upstream branch.  This can be used to avoid a possibly very
> +	expensive computation on extremely large repositories.
> ++
> +	In porcelain V2 format, the 'branch.ab' line will not be present.
> +

This second paragraph after the "+" continuation shouldn't be indented (sadly it makes the source much uglier, but it's one of the vagaries of asciidoc).

-Peff
Previous: Jeff HostetlerNext: Jeff King
Message 12 of 17 in “Add --no-ahead-behind to status”
  1. 0/4 Add --no-ahead-behind to statusJeff Hostetler, Dec 20, 2017
  2. 3/4 status: update short status to use --no-ahead-behindJeff Hostetler, Dec 20, 2017
  3. Jeff KingDec 20, 2017
  4. Jeff HostetlerDec 21, 2017
  5. Jeff KingDec 21, 2017
  6. Jeff HostetlerDec 21, 2017
  7. 2/4 stat_tracking_info: return +1 when branch and upstream differJeff Hostetler, Dec 20, 2017
  8. Jeff KingDec 20, 2017
  9. Jeff KingDec 20, 2017
  10. Jeff HostetlerDec 21, 2017
  11. 1/4 status: add --no-ahead-behind to porcelain V2Jeff Hostetler, Dec 20, 2017
  12. Jeff KingDec 20, 2017
  13. Jeff KingDec 20, 2017
  14. Jeff HostetlerDec 20, 2017
  15. 4/4 status: support --no-ahead-behind in long status format.Jeff Hostetler, Dec 20, 2017
  16. Jeff KingDec 20, 2017
  17. Jeff KingDec 20, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.