From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: git@vger.kernel.org, gitster@pobox.com
Cc: Jakub Narebski <jnareb@gmail.com>, Matthieu Moy <Matthieu.Moy@imag.fr>
Subject: [PATCH v2] RelNotes/1.8.5: direct script writers to "git status --porcelain"
Date: Thu, 26 Sep 2013 20:33:40 +0200 [thread overview]
Message-ID: <1380220420-27064-1-git-send-email-Matthieu.Moy@imag.fr> (raw)
In-Reply-To: <loom.20130926T201754-563@post.gmane.org>
Signed-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>
---
Jakub Narebski <jnareb@gmail.com> writes:
> Perhaps "to use instead ..." would be easier to understand than
> proposed "to use ..., instead." (with "..." being one line long).
Actually, I had the version below staged, but forgot to "commit
--amend" before sending. Should be clear enough.
Documentation/RelNotes/1.8.5.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/RelNotes/1.8.5.txt b/Documentation/RelNotes/1.8.5.txt
index ac5c3fa..e295266 100644
--- a/Documentation/RelNotes/1.8.5.txt
+++ b/Documentation/RelNotes/1.8.5.txt
@@ -96,6 +96,9 @@ UI, Workflows & Features
* "git status" now omits the prefix to make its output a comment in a
commit log editor, which is not necessary for human consumption.
+ Scripts that parse the output of "git status" are advised to use
+ "git status --porcelain" instead. Its format is both easier to
+ parse and stable.
* Make "foo^{tag}" to peel a tag to itself, i.e. no-op., and fail if
"foo" is not a tag. "git rev-parse --verify v1.0^{tag}" would be
--
1.8.4.474.g128a96c
next prev parent reply other threads:[~2013-09-27 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 13:23 [PATCH] RelNotes/1.8.5: direct script writers to "git status --porcelain" Matthieu Moy
2013-09-26 18:19 ` Jakub Narebski
2013-09-26 18:33 ` Matthieu Moy [this message]
2013-09-26 20:45 ` Keshav Kini
2013-09-28 0:08 ` Jonathan Nieder
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=1380220420-27064-1-git-send-email-Matthieu.Moy@imag.fr \
--to=matthieu.moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
/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).