W dniu 01.08.2016 o 17:39, Jeff Hostetler pisze: > 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html