jira-importer commented on issue #979: URL: https://github.com/apache/maven-scm/issues/979#issuecomment-2964637089
**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** commented From http://git-scm.com/docs/git-status: > ## Porcelain Format > > The porcelain format is similar to the short format, but is guaranteed not to change in a backwards-incompatible way between Git versions or based on user configuration. This makes it ideal for parsing by scripts. The description of the short format above also describes the porcelain format, with a few exceptions: > > 1.The user's color.status configuration is not respected; color will always be off. > 2.The user's status.relativePaths configuration is not respected; paths shown will always be relative to the repository root. > > There is also an alternate \-z format recommended for machine parsing. In that format, the status field is the same, but some other things change. First, the '->' is omitted from rename entries and the field order is reversed (e.g 'from -> to' becomes 'to from'). Second, a NUL (ASCII 0) follows each filename, replacing space as a field separator and the terminating newline (but a space still separates the status field from the first filename). Third, filenames containing special characters are not specially formatted; no quoting or backslash-escaping is performed. So yes, this looks interesting. However, I'm missing when both options were introduced. IIRC we now assume at least Git 1.8, although the SCM-API has no way to verify this (yet). If the `\-z` is supported for quite some time, it would probably be better to use it. The `GitStatusConsumer` has already quite some tests, so you should have good feedback on your changes. Looking forward on that patch. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
