git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nazri Ramliy <ayiehere@gmail.com>
To: git@vger.kernel.org
Cc: nazri <ayiehere@gmail.com>
Subject: [PATCH] Man page section reference should be in uppercase
Date: Tue, 25 May 2010 11:01:24 +0800	[thread overview]
Message-ID: <1274756484-27867-1-git-send-email-ayiehere@gmail.com> (raw)

From: nazri <ayiehere@gmail.com>

The advice given by git push when doing a non-fast-forward push refers
to the section 'Note about fast-forwards' in the git-push(1) man page.

The section name should really be all in uppercase, as in 'NOTE ABOUT
FAST-FORWARDS' because that is how it is shown by git push --help.

Signed-off-by: Nazri Ramliy <ayiehere@gmail.com>
---
 builtin/push.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/builtin/push.c b/builtin/push.c
index f4358b9..0694200 100644
--- a/builtin/push.c
+++ b/builtin/push.c
@@ -130,8 +130,8 @@ static int push_with_options(struct transport *transport, int flags)
 
 	if (nonfastforward && advice_push_nonfastforward) {
 		fprintf(stderr, "To prevent you from losing history, non-fast-forward updates were rejected\n"
-				"Merge the remote changes before pushing again.  See the 'Note about\n"
-				"fast-forwards' section of 'git push --help' for details.\n");
+				"Merge the remote changes before pushing again.  See the 'NOTE ABOUT\n"
+				"FAST-FORWARDS' section of 'git push --help' for details.\n");
 	}
 
 	return 1;
-- 
1.7.1.rc1.21.gf3bd6

             reply	other threads:[~2010-05-25  3:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-25  3:01 Nazri Ramliy [this message]
2010-05-25 18:45 ` [PATCH] Man page section reference should be in uppercase Dévai Tamás
     [not found]   ` <AANLkTilKSLCGMgHwB4TdojtemnxYLrGsAJGHQcLJNVwL@mail.gmail.com>
2010-05-26  8:33     ` Fwd: " Nazri Ramliy
2010-05-27 19:50       ` 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=1274756484-27867-1-git-send-email-ayiehere@gmail.com \
    --to=ayiehere@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).