Re: [PATCH 10/10] clone: accept config options on the command line

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jun 9, 2011 at 17:57, Jeff King <peff@xxxxxxxx> wrote:
> 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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]