![]() When cloning from servers that support it, Mercurial may fetch the tipmost head of the default branch i. the revision marked with the bookmark, if present h. the tipmost head specified with the url#branch source syntax g. the changeset specified with -u (if a branch name, this means the latest and the source repository is local, the first parent of the source null if -U or the source repository has no changesets b. Mercurial will update the working directory to the firstĪ. In theseĬases, use the -pull option to avoid hardlinking. Some filesystems, such asĪFS, implement hardlinking incorrectly, but do not report errors. Repository data, not to the working directory). Note Specifying a tag will include the tagged changeset but not the changesetįor efficiency, hardlinks are used for cloning whenever the sourceĪnd destination are on the same filesystem (note this applies only to the The remote or a legacy Mercurial client may not be able to clone from a Locally: a modern client may inherit legacy or inefficient storage used by A side-effect of -streamĬlones is that storage settings and requirements on the remote are applied Is plentiful, especially for larger repositories. This can result in substantially faster clones where I/O throughput ![]() ![]() However, it often increases the transferred data size byģ0-40%. This significantly reduces the CPU cost of a clone both remotelyĪnd locally. stream activates a different clone mode thatĮssentially copies repository files from the remote with minimal data In normal clone mode, the remote normalizes repository data into aĬommon exchange format and the receiving end translates this data into its Options (or 'clone src#rev dest') imply -pull, even for local source Will contain only the specified changesets and their ancestors. Identifiers with -r/-rev or branches with -b/-branch. To pull only a subset of changesets, specify one or more revisions U/-noupdate to create a clone with no working directory. To check out a particular version, use -u/-update, or Revision will be checked out in the new repository by default. If the source repository has a bookmark called set, that hg/hgrc will be created on the remote side. For ssh:// destinations, no working directory or Only local paths and ssh:// URLs are supported asĭestinations. hg/hgrc file, as the default to be used for future pulls. ![]() The location of the source is added to the new repository's If no destination directory name is specified, it defaults to the marked option can be specified multiple times COMMANDS ¶ Repository creation ¶ clone ¶Ĭreate a copy of an existing repository in a new directory. noninteractive do not prompt, automatically pick the first choice for all prompts -q, -quiet suppress output -v, -verbose enable additional output -color when to colorize (boolean, always, auto, never, or debug) -config set/override config option (use 'section.name=value') -debug enable debugging output -debugger start debugger -encoding set the charset encoding (default: UTF-8) -encodingmode set the charset encoding mode (default: strict) -traceback always print a traceback on exception -time time how long the command takes -profile print command execution profile -version output version information and exit -h, -help display help and exit -hidden consider hidden changesets -pager when to paginate (boolean, always, auto, or never) (default: auto) R, -repository repository root directory or name of overlay bundle file -cwd change working directory -y,
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |