Re: git-status -- trying to understand all possible states

2014-04-02 Thread Matthieu Moy
Jonathan Nieder writes: > - Please use --porcelain (implied by -z in the absence of another >format option) instead of --short. --short is meant to be human >readable and details of the output might change some day. It already does: part of the output may be translated to non-english.

Re: git-status -- trying to understand all possible states

2014-04-01 Thread Michael Toy
On Apr 1, 2014, at 2:37 PM, Junio C Hamano wrote: >> D Mdeleted from index > > I doubt this is possible in practice ... > >> D Dunmerged, both deleted >> A Uunmerged, added by us >> U Aunmerged, added by them > > ... you would not see t

Re: git-status -- trying to understand all possible states

2014-04-01 Thread Jonathan Nieder
Michael Toy wrote: > https://gist.github.com/the-michael-toy/9907309 Two nits: - Please use --porcelain (implied by -z in the absence of another format option) instead of --short. --short is meant to be human readable and details of the output might change some day. - Depending on what

Re: git-status -- trying to understand all possible states

2014-04-01 Thread Junio C Hamano
Michael Toy writes: > Of the 24 possibilities (not counting ignored) in git-status, > there are 7 that I can't figure out how to generate. As the post [*1*] that triggered e92e9cd3 (Documentation improvements for the description of short format., 2010-04-23), which is where the bulk of the forma

git-status -- trying to understand all possible states

2014-04-01 Thread Michael Toy
I also have this question posted to stack overflow ( http://stackoverflow.com/questions/22792906/how-do-i-produce-every-possible-git-status ), but perhaps this is a better place to ask this question. In working on some code which provides an interface to existing git repositories the question I