From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] RelNotes/1.8.5: direct script writers to "git status --porcelain"
Date: Thu, 26 Sep 2013 18:19:35 +0000 (UTC) [thread overview]
Message-ID: <loom.20130926T201754-563@post.gmane.org> (raw)
In-Reply-To: 1380201815-14140-1-git-send-email-Matthieu.Moy@imag.fr
Matthieu Moy <Matthieu.Moy <at> imag.fr> writes:
> * "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", which is both easier to parse and stable,
> + instead.
Good addition.
Perhaps "to use instead ..." would be easier to understand than
proposed "to use ..., instead." (with "..." being one line long).
--
Jakub Narebski.
next prev parent reply other threads:[~2013-09-26 18:20 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 [this message]
2013-09-26 18:33 ` [PATCH v2] " Matthieu Moy
2013-09-26 20:45 ` [PATCH] " 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=loom.20130926T201754-563@post.gmane.org \
--to=jnareb@gmail.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).