18:06 git clone depth of 0 not possible Stefan Beller ^ raw reply related 29+ messages in thread + below, the cloned repository will not be shallow.Ĭlone only the history leading to the tip of a single branch, With a long history, and would want to send in fixes It, nor push from nor into it), but is adequate if youĪre only interested in the recent history of a large project +++ -186,7 +186,8 objects from the source repository into a pack in the cloned repository. ![]() 7:33 ` git clone depth of 0 not possible Duy NguyenĢ siblings, 0 replies 29+ messages in threadĭiff -git a/Documentation/git-clone.txt b/Documentation/git-clone.txt 6:28 ` git clone depth of 0 not possible Jonathan Nieder 18:06 git clone depth of 0 not possible Stefan 18:06 ` Stefan Beller * Documentation on depth option in git clone. So I documented the current behavior, see attached patch.ĭocumentation on depth option in git clone.ġ file changed, 2 insertions(+), 1 deletion(-) Uses value 0 for another meaning, so it would have need changes atĪll places, where the transport options depth is being used The depth variable in git_transport_options struct (file transport.h) I had no good idea how to add this behavior to git clone as The minimum number of commits is 2, caused by depth=1. only one commit in that repository after cloning. To: schlotter, gitster, Ralf.Wildenhues, git +Cc: Stefan BellerĬurrently it is not possible to have a shallow depth of ` (2 more replies) 0 siblings, 3 replies 29+ messages in threadįrom: Stefan Beller 18:06 UTC ( / raw) 18:06 ` Documentation on depth option in git clone Stefan Beller mailing list mirror (one of many) help / color / mirror / code / Atom feed * git clone depth of 0 not possible. This request is similar to but expands upon it significantly.Git clone depth of 0 not possible. This defeats the purpose of a shallow clone Regardless of what depth you clone to, when SmartGit does a subsequent fetch, it does not specific the desired depth, so you end up pulling the entire repo anyhow.No support for -unshallow, -update-shallow, or -deepen-shallow when fetchingīugs (as of SmartGit 17.1 preview 6 #11041):.No way to change the desired depth after cloning (that I could find), to use subsequent fetches/pulls to trim or fill-in the history.No support for -shallow-exclude in clone/fetch/pull.There's only an option to clone to a depth, and not "clone since date" (the "-shallow-since=" option in git clone/fetch).No support for choosing -shallow-submodules vs -no-shallow-submodules when cloning.There is no support for fetching all heads so long as they are within the desired commit depth (the "-no-single-branch" option in 'git clone'). If you wish to clone to a specific depth, you only have the option of doing so if you un-check the "fetch all heads and tags".However, this is not sufficient for fully supporting a 'shallow repo' workflow, for the following reasons: SmartGit currently has an option, when cloning a repo, to clone only to a specific depth. This lets developers pull down only a small amount of the history, making it faster to work locally (due to less data in the repo that needs to be maintained), and also avoiding the need to pull huge amounts of data over the network when cloning. Since git 1.9 (with better support since 2.5), git has fully supported shallow repos (you can push/pull to/from the remote, etc), and is now very configurable. ![]() Shallow repos are extremely useful when working with huge repositories with long histories and large amounts of data (like binaries).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |