![]() > all places, where the transport options depth is being used > uses value 0 for another meaning, so it would have need changes at > 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 7:37 ` Junio C Hamano 2 siblings, 1 reply 29+ messages in thread 6:28 ` git clone depth of 0 not possible Jonathan 7:33 ` Duy Nguyen 'next' for a while and push it out together with other "2.0" topics I do not mind carrying such a (technially) backward incompatibleĬhange in jn/clone-2.0-depth-off-by-one branch, keep it cooking in Not be transferred and recorded as the shallow boundary in the Magically start meaning "only the tip its immediate parents will Send over the wire the number that corresponded to the old "depthġ"), I do not think anything will break, and then -depth=0 may the number we receive from the user will beįudged, so that user's "depth 1" that used to mean "the tip and oneīehind it" is expressed as "depth 2" at the end-user level, and we Would anything break if we were to make -depth=1 meanĪs long as we do not change the meaning of the "shallow" count going To: Jonathan Nieder +Cc: Stefan Beller, schlotter, Ralf.Wildenhues, git 7:38 ` Duy Nguyen 0 siblings, 2 replies 29+ messages in threadįrom: Junio C Hamano 6:54 UTC ( / raw) 6:28 ` git clone depth of 0 not possible Jonathan 6:54 ` Junio C Hamano Would anything break if we were to make -depth=1 mean > The minimum number of commits is 2, caused by depth=1. only one commit in that repository after cloning. > Currently it is not possible to have a shallow depth of ![]() To: Stefan Beller +Cc: schlotter, gitster, Ralf.Wildenhues, git 18:06 ` Documentation on depth option in git clone Stefan 6:28 ` Jonathan NiederĢ siblings, 1 reply 29+ messages in threadįrom: Jonathan Nieder 6:28 UTC ( / raw) 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. 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.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |