Phil Hord <ho...@cisco.com> 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
> # tokens only?
> $ git status --tree --porcelain
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.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html