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

Re: [PATCH v3 7/8] status: update git-status.txt for --porcelain=v2

From
Jakub Narębski <jnareb@gmail.com>
Date
Aug 2, 2016, 15:19 UTC
Message-ID
<4afec4ce-ecb4-dcce-b8f5-c37844d963d8@gmail.com>
In-Reply-To
<579F6D3A.3010704@jeffhostetler.com>
W dniu 01.08.2016 o 17:39, Jeff Hostetler pisze:
Show 28 quoted lines
> On 07/30/2016 01:22 PM, Jakub Narębski wrote:
>> W dniu 26.07.2016 o 23:11, Jeff Hostetler pisze:
>>
>> This is a nice change, available because of lack of backward
>> compatibility with v1.  The porcelain v2 format branch-related
>> information could be enhanced without risk of breaking parsers,
>> or having new information put at the end even if it does not fit
>> there (like in previous iteration).
>>
>> One thing that can serve as goal for the series is using the
>> question: would it make __git_ps1() from git-prompt.sh be able
>> to render fully decorated prompt with all bells and whistles,
>> and with all combinations of options.  Thus beside upstream
>> in the future we might want SVN upstream, and/or pushed-to
>> remote branch (and remote push upstream repository), etc.
>>
>> But that's for the future (and it is possible for the future)...
>>
> 
> Yes, I was hoping to be able to simplify and/or speed up
> __git_ps1() with this data.  "Namespacing" the branch data
> here.  And then later add the state data (in a merge,
> in a rebase, and etc.) in a series of "# state.*" headers.
> And so on, until we get everything that __git_ps1() needs.
> However, to really make that work, we might want to add
> a --no-scan (or minimial scan) option, to just return the
> header data, since __git_ps1() doesn't care about the list
> of changes.

But __git_ps1() with GIT_PS1_SHOWDIRTYSTATE would want to know if there are unstaged and staged changes, and with GIT_PS1_SHOWUNTRACKEDFILES it would want to know if there are untracked (unknown) files, isn't it?

And GIT_PS1_SHOWSTASHSTATE would want to know if there is
something stashed, but I guess it is outside the remit of
git-status...
 
Also, __git_ps1() uses colors from git-status, so if it
is switched to use --porcelain=v2, then there should be an
option to turn the color on, isn't it?
-- 
Jakub Narębski
Previous: Jeff HostetlerNext: Jeff Hostetler
Message 9 of 13 in “status: V2 porcelain status”
  1. 0/8 status: V2 porcelain statusJeff Hostetler, Jul 26, 2016
  2. 2/8 status: cleanup API to wt_status_printJeff Hostetler, Jul 26, 2016
  3. 3/8 status: support --porcelain[=<version>]Jeff Hostetler, Jul 26, 2016
  4. 4/8 status: per-file data collection for --porcelain=v2Jeff Hostetler, Jul 26, 2016
  5. 5/8 status: print per-file porcelain v2 status dataJeff Hostetler, Jul 26, 2016
  6. 7/8 status: update git-status.txt for --porcelain=v2Jeff Hostetler, Jul 26, 2016
  7. Jakub NarębskiJul 30, 2016
  8. Jeff HostetlerAug 1, 2016
  9. Jakub NarębskiAug 2, 2016
  10. Jeff HostetlerAug 2, 2016
  11. 6/8 status: print branch info with --porcelain=v2 --branchJeff Hostetler, Jul 26, 2016
  12. 8/8 status: tests for --porcelain=v2Jeff Hostetler, Jul 26, 2016
  13. 1/8 status: rename long-format print routinesJeff Hostetler, Jul 26, 2016

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.