git-status -- trying to understand all possible states

I had was "what actions should I present to a user", which lead to the question, "what does a user need to do to generate that condition", which lead to developing this gist: https://gist.github.com/the-michael-toy/9907309 ... which is a ruby script which tries to produce

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

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