From: "J. Bruce Fields" <bfields@fieldses.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: git push -f documentation
Date: Sun, 29 Jan 2006 20:40:50 -0500 [thread overview]
Message-ID: <20060130014050.GA18945@fieldses.org> (raw)
Surely the documentation here is exactly backwards? Or am I
missing something?--b.
---
Documentation/git-push.txt | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
1391326bf55bc9a9deb52a872671f29c70c0a4de
diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
index 365cfd4..a0ef61d 100644
--- a/Documentation/git-push.txt
+++ b/Documentation/git-push.txt
@@ -35,10 +35,10 @@ include::pull-fetch-param.txt[]
line.
-f, \--force::
- Usually, the command refuses to update a local ref that is
- not an ancestor of the remote ref used to overwrite it.
- This flag disables the check. What this means is that the
- local repository can lose commits; use it with care.
+ Usually, the command refuses to update a remote ref that is
+ not a descendent 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.
Author
--
0.99.8b.g3480-dirty
next reply other threads:[~2006-01-30 1:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 1:40 J. Bruce Fields [this message]
2006-01-30 1:53 ` git push -f documentation 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=20060130014050.GA18945@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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