From: Mark Jason Dominus <mjd@plover.com>
To: git@vger.kernel.org
Subject: Bug report : git-status manual fibs about semantics of --porcelain
Date: Thu, 19 May 2011 14:01:12 -0400 [thread overview]
Message-ID: <30543.1305828072@plover.com> (raw)
The 1.7.5.1 manual says:
--porcelain::
Give the output in a stable, easy-to-parse format for scripts.
Currently this is identical to --short output, but is guaranteed
not to change in the future, making it safe for scripts.
However, this is not actually true. --porcelain differs from --short
in at least two ways, one of them significant.
--short is colorized when color.status = auto, while --porcelain is
not.
More importantly, --short reports file paths relative to the
current directory, while --porcelain reports file paths relative to
the root of the repository.
All of this was the case in 1.7.0.4 also, and presumably the versions
in between.
Mark Jason Dominus mjd@plover.com
next reply other threads:[~2011-05-19 18:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 18:01 Mark Jason Dominus [this message]
2011-05-27 2:31 ` [PATCH 1/4] docs: minor grammar fixes to git-status Jeff King
2011-05-27 2:31 ` [PATCH 2/4] docs: update status --porcelain format Jeff King
2011-05-27 2:32 ` [PATCH 3/4] docs: make sure literal "->" isn't converted to arrow Jeff King
2011-05-27 2:33 ` [PATCH 4/4] docs: fix some antique example output Jeff King
2011-05-27 5:16 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=30543.1305828072@plover.com \
--to=mjd@plover.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).