From: John Tapsell <johnflux@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: [PATCH 5/6] Change output "error: " to "Error: " etc
Date: Thu, 19 Feb 2009 07:36:49 +0000 [thread overview]
Message-ID: <200902190736.49161.johnflux@gmail.com> (raw)
All the error messages starting "Error: " begin with a captial E, except
in one place. This commit fixes this, making the output look more
consistent. At the moment a failed push, say, looks like:
Error: cannot lock existing info/refs
error: failed to push some refs to 'some repository'
Signed-off-by: John Tapsell <johnflux@gmail.com>
---
usage.c | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/usage.c b/usage.c
index 24f5fc0..acc4ee1 100644
--- a/usage.c
+++ b/usage.c
@@ -14,24 +14,24 @@ static void report(const char *prefix, const char *err, va_list params)
static NORETURN void usage_builtin(const char *err)
{
- fprintf(stderr, "usage: %s\n", err);
+ fprintf(stderr, "Usage: %s\n", err);
exit(129);
}
static NORETURN void die_builtin(const char *err, va_list params)
{
- report("fatal: ", err, params);
+ report("Fatal: ", err, params);
exit(128);
}
static void error_builtin(const char *err, va_list params)
{
- report("error: ", err, params);
+ report("Error: ", err, params);
}
static void warn_builtin(const char *warn, va_list params)
{
- report("warning: ", warn, params);
+ report("Warning: ", warn, params);
}
/* If we are in a dlopen()ed .so write to a global variable would segfault
--
1.6.2.rc1.3.g7d31b.dirty
next reply other threads:[~2009-02-19 7:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 7:36 John Tapsell [this message]
2009-02-19 8:14 ` [PATCH 5/6] Change output "error: " to "Error: " etc Thomas Rast
2009-02-19 8:17 ` Jeff King
2009-02-19 12:07 ` [PATCH] http-push: using error() and warning() as appropriate Miklos Vajna
2009-02-19 12:21 ` Jeff King
2009-02-19 12:52 ` [PATCH 0/8] fprintf(stderr, "warning: ") -> warning() patches Miklos Vajna
2009-02-19 12:53 ` [PATCH 1/8] builtin-apply: use warning() instead of fprintf(stderr, "warning: ") Miklos Vajna
2009-02-20 3:02 ` Jeff King
2009-02-20 6:11 ` Junio C Hamano
2009-03-22 11:36 ` Miklos Vajna
2009-03-22 21:58 ` Junio C Hamano
2009-03-24 1:09 ` [PATCH 0/9] fprintf(stderr, "warning: ") -> warning() patches Miklos Vajna
2009-03-24 1:09 ` [PATCH 1/9] http-push: using error() and warning() as appropriate Miklos Vajna
2009-03-24 1:09 ` [PATCH 2/9] builtin-apply: use warning() instead of fprintf(stderr, "warning: ") Miklos Vajna
2009-03-24 1:25 ` Erik Faye-Lund
2009-03-24 1:09 ` [PATCH 3/9] builtin-checkout: " Miklos Vajna
2009-03-24 1:09 ` [PATCH 4/9] builtin-fetch-pack: " Miklos Vajna
2009-03-24 1:09 ` [PATCH 5/9] builtin-init-db: " Miklos Vajna
2009-03-24 1:09 ` [PATCH 6/9] builtin-rm: " Miklos Vajna
2009-03-24 1:09 ` [PATCH 7/9] builtin-show-branch: " Miklos Vajna
2009-03-24 1:09 ` [PATCH 8/9] builtin-show-ref: " Miklos Vajna
2009-03-24 1:09 ` [PATCH 9/9] refs: " Miklos Vajna
2009-03-24 1:17 ` Erik Faye-Lund
2009-03-24 1:23 ` Miklos Vajna
2009-03-24 1:28 ` Erik Faye-Lund
2009-03-24 7:35 ` [PATCH 0/9] fprintf(stderr, "warning: ") -> warning() patches Jeff King
2009-03-24 8:01 ` Junio C Hamano
2009-02-20 9:41 ` [PATCH 1/8] builtin-apply: use warning() instead of fprintf(stderr, "warning: ") Miklos Vajna
2009-02-19 12:53 ` [PATCH 2/8] builtin-checkout: " Miklos Vajna
2009-02-19 12:53 ` [PATCH 3/8] builtin-fetch-pack: " Miklos Vajna
2009-02-19 12:54 ` [PATCH 4/8] builtin-init-db: " Miklos Vajna
2009-02-19 12:54 ` [PATCH 5/8] builtin-rm: " Miklos Vajna
2009-02-19 12:54 ` [PATCH 6/8] builtin-show-branch: " Miklos Vajna
2009-02-19 12:55 ` [PATCH 7/8] builtin-show-ref: " Miklos Vajna
2009-02-19 12:55 ` [PATCH 8/8] refs: " Miklos Vajna
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=200902190736.49161.johnflux@gmail.com \
--to=johnflux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.