Andrew's git
/
gitweb.git
/ diff
summary
|
log
|
commit
| diff |
tree
commit
grep
author
committer
pickaxe
?
re
user-manual: give 'git push -f' as an alternative to +master
author
W. Trevor King
<wking@tremily.us>
Mon, 18 Feb 2013 00:15:55 +0000
(19:15 -0500)
committer
Junio C Hamano
<gitster@pobox.com>
Mon, 18 Feb 2013 08:48:37 +0000
(
00:48
-0800)
This mirrors existing language in the description of 'git fetch'.
Signed-off-by: W. Trevor King <wking@tremily.us>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/user-manual.txt
patch
|
blob
|
history
raw
|
patch
|
inline
| side by side (parent:
e9b4908
)
diff --git
a/Documentation/user-manual.txt
b/Documentation/user-manual.txt
index 74dd82ab7ad7215f589f92376c9549082975d3a7..a546b10ee1c6a12bc9e856f137f65db6e4bf1ba0 100644
(file)
--- a/
Documentation/user-manual.txt
+++ b/
Documentation/user-manual.txt
@@
-2045,6
+2045,13
@@
branch name with a plus sign:
$ git push ssh://yourserver.com/~you/proj.git +master
-------------------------------------------------
$ git push ssh://yourserver.com/~you/proj.git +master
-------------------------------------------------
+Note the addition of the `+` sign. Alternatively, you can use the
+`-f` flag to force the remote update, as in:
+
+-------------------------------------------------
+$ git push -f ssh://yourserver.com/~you/proj.git master
+-------------------------------------------------
+
Normally whenever a branch head in a public repository is modified, it
is modified to point to a descendant of the commit that it pointed to
before. By forcing a push in this situation, you break that convention.
Normally whenever a branch head in a public repository is modified, it
is modified to point to a descendant of the commit that it pointed to
before. By forcing a push in this situation, you break that convention.