documentation: add missing article
Diff best viewed with --color-diff. Signed-off-by: Elijah Newren <newren@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:

committed by
Junio C Hamano

parent
3771d00257
commit
0a4f051f93
@ -80,7 +80,7 @@ configuration which'll amend these rules, and nothing like a
|
||||
+
|
||||
As with pushing with linkgit:git-push[1], all of the rules described
|
||||
above about what's not allowed as an update can be overridden by
|
||||
adding an optional leading `+` to a refspec (or using `--force`
|
||||
adding an optional leading `+` to a refspec (or using the `--force`
|
||||
command line option). The only exception to this is that no amount of
|
||||
forcing will make the `refs/heads/*` namespace accept a non-commit
|
||||
object.
|
||||
@ -88,7 +88,7 @@ object.
|
||||
[NOTE]
|
||||
When the remote branch you want to fetch is known to
|
||||
be rewound and rebased regularly, it is expected that
|
||||
its new tip will not be descendant of its previous tip
|
||||
its new tip will not be a descendant of its previous tip
|
||||
(as stored in your remote-tracking branch the last time
|
||||
you fetched). You would want
|
||||
to use the `+` sign to indicate non-fast-forward updates
|
||||
|
Reference in New Issue
Block a user