From: Junio C Hamano Date: Thu, 29 May 2014 19:53:28 +0000 (-0700) Subject: fetch doc: update note on '+' in front of the refspec X-Git-Tag: v2.1.0-rc0~93^2~7 X-Git-Url: https://git.lorimer.id.au/gitweb.git/diff_plain/f471dbc5feeefd3a761f311d3efa7b1a987bcb13?ds=inline;hp=--cc fetch doc: update note on '+' in front of the refspec While it is not *wrong* per-se to say that pulling a rewound/rebased branch will lead to an unnecessary merge conflict, that is not what the leading "+" sign to allow non-fast-forward update of remote-tracking branch is at all. Helped-by: Marc Branchaud Signed-off-by: Junio C Hamano --- f471dbc5feeefd3a761f311d3efa7b1a987bcb13 diff --git a/Documentation/pull-fetch-param.txt b/Documentation/pull-fetch-param.txt index 18cffc25b8..41474c5dc7 100644 --- a/Documentation/pull-fetch-param.txt +++ b/Documentation/pull-fetch-param.txt @@ -24,15 +24,15 @@ is updated even if it does not result in a fast-forward update. + [NOTE] -If the remote branch from which you want to pull is -modified in non-linear ways such as being rewound and -rebased frequently, then a pull will attempt a merge with -an older version of itself, likely conflict, and fail. -It is under these conditions that you would want to use -the `+` sign to indicate non-fast-forward updates will -be needed. There is currently no easy way to determine -or declare that a branch will be made available in a -repository with this behavior; the pulling user simply +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 +(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 +will be needed for such branches. There is no way to +determine or declare that a branch will be made available +in a repository with this behavior; the pulling user simply must know this is the expected usage pattern for a branch. + [NOTE]