--- OLD/man1/git-clone.1 Thu Jan 1 00:00:00 1970 +++ NEW/man1/git-clone.1 Thu Jan 1 00:00:00 1970 @@ -17,9 +17,10 @@ .RS 4 .nf \fIgit clone\fR [\-\-template=] - [\-l] [\-s] [\-\-no\-hardlinks] [\-q] [\-n] [\-\-bare] [\-\-mirror] + [\-f] [\-l] [\-s] [\-\-no\-hardlinks] + [\-q] [\-n] [\-\-bare] [\-\-mirror] [\-o ] [\-u ] [\-\-reference ] - [\-\-depth ] [\-\-] [] + [\-\-depth ] [\-\-] .fi .RE .SH "DESCRIPTION" @@ -129,6 +130,15 @@ to keep track of the upstream repository, use \. .RE .PP +\-f, \-\-force +.RS 4 +Normally, the directory being cloned into must be either nonexistent or +empty. This option relaxes this restriction, allowing cloning into a +nonempty directory. This is a dangerous operation, as there is no +check to prevent overwriting existing files, but it simplifies some +unusual operations. +.RE +.PP \-\-upload\-pack , \-u .RS 4 When given, and the repository to clone from is accessed via ssh, this specifies a non\-default path for the command run on the other end\. @@ -156,7 +166,9 @@ .PP .RS 4 -The name of a new directory to clone into\. The "humanish" part of the source repository is used if no directory is explicitly given ("repo" for "/path/to/repo\.git" and "foo" for "host\.xz:foo/\.git")\. Cloning into an existing directory is only allowed if the directory is empty\. +The name of a new directory to clone into. Cloning into an existing +directory is normally allowed only if the directory is empty, but see +the \-f option. .RE .SH "GIT URLS" One of the following notations can be used to name the remote repository: