Phil Hord [off-list ref] writes:
# tokens and short-status
$ git status --tree --short
## changed-files
M foo.txt
Hrm, how will the existing readers of the output avoid getting
confused by this overloading of "##", which has meant the current
branch information?
# tokens only?
$ git status --tree --porcelain
changed-files
It probably is simpler for parsers of the --porcelain format if you
(1) always used first two bytes as the record type, and (2) avoided
using "##" that is already used for the tree-wide status.
Just a thought.