[PATCH] Document git-fetch options
authorSergey Vlasov <vsu@altlinux.ru>
Wed, 14 Sep 2005 12:48:05 +0000 (16:48 +0400)
committerJunio C Hamano <junkio@cox.net>
Thu, 15 Sep 2005 20:16:31 +0000 (13:16 -0700)
Add documentation for git-fetch options

Signed-off-by: Junio C Hamano <junkio@cox.net>
Documentation/git-fetch.txt
Documentation/pull-fetch-param.txt
index 017f6466010f31d9084257d3708aee18c6049abf..8c1cc0704836b1ebf046a538329a9c0e3e9dc399 100644 (file)
@@ -26,6 +26,12 @@ OPTIONS
 -------
 include::pull-fetch-param.txt[]
 
+-u, \--update-head-ok::
+       By default 'git-fetch' refuses to update the head which
+       corresponds to the current branch.  This flag disables the
+       check.  Note that fetching into the current branch will not
+       update the index and working directory, so use it with care.
+
 
 Author
 ------
index 8f6b68cb5514958570196b4c3f725467c0279ed3..8642182c89109b50eecc741cc71dde90f27d9048 100644 (file)
           <ref>: when pulling/fetching, and <ref>:<ref> when
           pushing.  That is, do not store it locally if
           fetching, and update the same name if pushing.
+
+-a, \--append::
+       Append ref names and object names of fetched refs to the
+       existing contents of $GIT_DIR/FETCH_HEAD.  Without this
+       option old data in $GIT_DIR/FETCH_HEAD will be overwritten.
+
+-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.