From: Matthew Rothenberg <mrothenberg@gmail.com>
Date: Mon, 09 Mar 2015 23:40:43 GMT
Subject: Re: Efficient parsing of `status -z` output
Message-ID: <CAMJduDvuBF6KwLjmnxmMgfeSYfO6uDVfnkF=VTLTr8t8qowb0w@mail.gmail.com>
In-Reply-To: <20150309064939.GA30819@peff.net>

On Mon, Mar 9, 2015 at 2:49 AM, Jeff King <peff@peff.net> wrote:
>   $ git init
>   $ seq 1 1000 >file && git add file && git commit -m base
>   $ mv file other
>   $ echo foo >file
>   $ git add .
>   $ git status --short
>   M  file
>   C  file -> other

Fantastic, I am able to replicate with these steps and will build
tests around this case.

For future proofing, from the documentation for git status is appears
the other two codes I would want to check for in addition to 'C '
(which this test cases generates) may be 'CM' and 'CD'? And all of
those should always have the additional PATH2 column present?

Thank you for your help!