From: A.J.Delaney@brighton.ac.uk
To: git@vger.kernel.org
Subject: [Patch] Error message grammar
Date: Wed, 02 Mar 2011 21:37:18 +0000 [thread overview]
Message-ID: <1299101838.2807.54.camel@SillyFace> (raw)
[-- Attachment #1: Type: text/plain, Size: 437 bytes --]
Dear all,
I got an error message from git and the grammar tweaked me (maybe it's
just the mood I'm in). I'm not subscribed to the list.
--
Aidan
___________________________________________________________
This email has been scanned by MessageLabs' Email Security
System on behalf of the University of Brighton.
For more information see http://www.brighton.ac.uk/is/spam/
___________________________________________________________
[-- Attachment #2: 0001-Fixed-grammar-on-two-error-messages.patch --]
[-- Type: text/x-patch, Size: 932 bytes --]
>From 743d2eda72eb393bee41ac98a3994d110916b08a Mon Sep 17 00:00:00 2001
From: Aidan Delaney <aidan@phoric.eu>
Date: Wed, 2 Mar 2011 21:30:36 +0000
Subject: [PATCH] Fixed grammar on two error messages.
---
builtin/commit.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/builtin/commit.c b/builtin/commit.c
index 355b2cb..d56ddeb 100644
--- a/builtin/commit.c
+++ b/builtin/commit.c
@@ -991,9 +991,9 @@ static int parse_and_validate_options(int argc, const char *argv[],
handle_untracked_files_arg(s);
if (all && argc > 0)
- die("Paths with -a does not make sense.");
+ die("Using paths with -a does not make sense.");
else if (interactive && argc > 0)
- die("Paths with --interactive does not make sense.");
+ die("Using paths with --interactive does not make sense.");
if (null_termination && status_format == STATUS_FORMAT_LONG)
status_format = STATUS_FORMAT_PORCELAIN;
--
1.7.4
next reply other threads:[~2011-03-02 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 21:37 A.J.Delaney [this message]
2011-03-02 22:03 ` [Patch] Error message grammar Matthieu Moy
2011-03-06 15:21 ` A.J.Delaney
2011-03-06 17:38 ` Matthieu Moy
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=1299101838.2807.54.camel@SillyFace \
--to=a.j.delaney@brighton.ac.uk \
--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).