![]() git/objects/info/alternates to obtain objects from the reference repository. If the reference repository is on the local machine, automatically setup Repository into a pack in the cloned repository. Repository, you can simply run git repack -a to copy all objects from the source If you want to break the dependency of a repository cloned with -s on its source It is safe, however, to run git gc, which uses the Note that running git repack without the -l option in a repository cloned with -s willĬopy objects from the source repository into a pack in the cloned repository, removing (See git-gc(1).) If these objects are removed and were referenced by theĬloned repository, then the cloned repository will become corrupt. Removed by normal Git operations (such as git commit) which automatically call git gc Repository, some objects may become unreferenced (or dangling). Use any other Git command that makes any existing commit unreferenced) in the source If you clone your repository using this option and then delete branches (or NOTE: this is a possibly dangerous operation do not use it unless you understand what The resulting repository starts out without any object of its own. git/objects/info/alternates to share the objects with the source When the repository to clone is on the local machine, instead of using hard links,Īutomatically setup. Optimize the cloning process from a repository on a local filesystem by copying files Make a back-up of your repository), but still avoid the usual "Git aware" transport To force copying instead of hardlinking (which may be desirable if you are trying to no-local will override the default when /path/to/repo is given, using the regular Then this flag is ignored (and we never use the local optimizations). If the repository is specified as a local path (e.g., /path/to/repo), this is theĭefault, and -local is essentially a no-op. git/objects/ directoryĪre hardlinked to save space when possible. "Git aware" transport mechanism and clones the repository by making a copy of HEAD andĮverything under objects and refs directories. ![]() When the repository to clone from is on a local machine, this flag bypasses the normal Under refs/remotes/origin and by initializing and This default configuration is achieved by creating references to the remote branch heads Into the current master branch, if any (this is untrue when "-single-branch" is given Out an initial branch that is forked from the cloned repository’s currently active branch.Īfter the clone, a plain git fetch without arguments will update all the remote-trackingīranches, and a git pull without arguments will in addition merge the remote master branch Ĭlones a repository into a newly created directory, creates remote-tracking branches forĮach branch in the cloned repository (visible using git branch -r), and creates and checks Git-clone - Clone a repository into a new directory
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |