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

Re: [PATCH 3/4] status: update short status to use --no-ahead-behind

From
JHJeff Hostetler <git@jeffhostetler.com>
Date
Dec 21, 2017, 14:18 UTC
Message-ID
<1c019725-7715-496e-bad6-9d47d2bae834@jeffhostetler.com>
In-Reply-To
<20171220162637.GC31149@sigill.intra.peff.net>
On 12/20/2017 11:26 AM, Jeff King wrote:
Show 14 quoted lines
> On Wed, Dec 20, 2017 at 02:42:44PM +0000, Jeff Hostetler wrote:
> 
>> From: Jeff Hostetler <jeffhost@microsoft.com>
>>
>> Teach "git status --short --branch" to use "--no-ahead-behind"
>> flag to skip computing ahead/behind counts for the branch and
>> its upstream and just report '[different]'.
> 
> How come "--short" and "--long" get this smaller bit of data, but
> "--porcelain=v2" just omits the line entirely?
> 
> I don't have a real preference for or against the "[different]" message
> myself, but if we can get the information cheaply, it seems odd not to
> provide it in all cases.

I was only thinking of VS usage. But you're right, I can include an alternate line with eq|neq since we already have the data on hand.

[...]
Show 10 quoted lines
>> +test_expect_success 'status -s -b --no-ahead-behind (diverged from upstream)' '
> 
> This patch will affect "git status --porcelain", too. That's not
> supposed to change in incompatible ways. I guess it's up for debate
> whether callers are meant to handle any arbitrary string inside the []
> (we already show "[gone]" for some cases), since AFAICT the format of
> the tracking info is left completely vague in the documentation.
> 
> (I'd also hope that everybody is using --porcelain=v2 if they can, but
> we should still avoid breaking v1).

I hadn't intended to alter V1 output. I'll disable the new feature when V1 is selected.

Thanks Jeff

Previous: Jeff KingNext: Jeff King
Message 4 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.