![]() 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) ![]() You can find more information at the section called “git-push(1)”.-R, -repository repository root directory or name of overlay bundle file -cwd change working directory -y, If the submodules are not pushed yet, it will try to push them. On-demand: Checks if the bounded commits of all submodules are present on the remote repositories. If any of the submodules are not pushed, the super project push will fail. Check: Checks if the bounded commits of all submodules are present on the remote repositories. This will select the remote branch automatically for pulling/pushing and merging.Īlways push to the selected remote archive for this local branchĪlways push to the selected remote branch for this local branch Set upstream/track remote branch: After a successful push, the tracking relationship will be set between the pushed local branch and its remote tracking branch. There is also explained how you can use several accounts at the same time for a remote. You can find more information about PuTTY and using SSH keys at Appendix F, Tips and tricks for SSH/PuTTY. Include Tags Also push tags to remote repository. This passes the traditional -force option of git push command. Use this option with Include Tags to overwrite tags. This does not check any server commits, so it is possible to lose unknown changes on the remote. This can cause the remote repository to lose commits use it with care. This passes -force-with-lease option of git push command.įorce This allows remote repository to accept an unsafe non-fast-forward push. Since git does not have remote-tracking tags, tags cannot be overwritten using this option. It checks if the server branch points to the same commit as the remote-tracking branch (known changes). This can prevent from losing unknown changes from other people on the remote. Force with lease This allows remote repository to accept a safer non-fast-forward push.
0 Comments
Leave a Reply. |