Re: [PATCH 10/10] clone: accept config options on the command line
From: Bert Wesarg <hidden>
Date: 2016-06-15 22:51:27
On Thu, Jun 9, 2011 at 17:57, Jeff King [off-list ref] wrote:
quoted hunk ↗ jump to hunk
diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt index b093e45..3e24064 100644 --- a/Documentation/git-clone.txt +++ b/Documentation/git-clone.txt@@ -159,6 +159,15 @@ objects from the source repository into a pack in the cloned repository.Specify the directory from which templates will be used; (See the "TEMPLATE DIRECTORY" section of linkgit:git-init[1].) +--config <key>=<value>:: +-c <key>=<value>:: + Set a configuration variable in the newly-cloned repository. The
Shouldn't this be 'newly-created repository', because the configuration variables are set before the actual cloning, but after initializing the new repository. Bert
+ key is in the same as expected by linkgit:git-config[1] (e.g., + `core.eol=true`). If multiple values are given for the same key, + each value will be written to the config file. This makes it + safe, for example, to add additional fetch refspecs to the + origin remote. + --depth <depth>:: Create a 'shallow' clone with a history truncated to the specified number of revisions. A shallow repository has a