From: Jyotirmoy Bhattacharya <jyotirmoy@jyotirmoy.net>
To: git@vger.kernel.org
Cc: Jyotirmoy Bhattacharya <jyotirmoy@jyotirmoy.net>
Subject: [PATCH] Fixed git-push manpage
Date: Sun, 5 Aug 2007 10:52:15 +0530 [thread overview]
Message-ID: <11862913353314-git-send-email-jyotirmoy@jyotirmoy.net> (raw)
In git-push it is the remote repository and not the
local repository which is fast forwarded. The description
of the -f option in the git-push manpage gets it the other
way round.
Signed-off-by: Jyotirmoy Bhattacharya <jyotirmoy@jyotirmoy.net>
---
Documentation/git-push.txt | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
index 74a0da1..0dd9caf 100644
--- a/Documentation/git-push.txt
+++ b/Documentation/git-push.txt
@@ -79,7 +79,7 @@ the remote repository.
-f, \--force::
Usually, the command refuses to update a remote ref that is
- not a descendant of the local ref used to overwrite it.
+ not an ancestor of the local ref used to overwrite it.
This flag disables the check. This can cause the
remote repository to lose commits; use it with care.
--
1.5.2.4
next reply other threads:[~2007-08-05 5:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 5:22 Jyotirmoy Bhattacharya [this message]
2007-08-05 5:35 ` [PATCH] Fixed git-push manpage 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=11862913353314-git-send-email-jyotirmoy@jyotirmoy.net \
--to=jyotirmoy@jyotirmoy.net \
--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).