On Fri, 15 Mar 2019, Duy Nguyen wrote: > On Fri, Mar 15, 2019 at 7:17 PM Robert P. J. Day <rpjday@xxxxxxxxxxxxxx> wrote: > > > > > > probably doing something idiotic but i'm enumerating variations of > > shallow cloning, and tried the following: > > > > $ git clone --shallow-exclude=master https://github.com/django/django.git > > Cloning into 'django'... > > fatal: the remote end hung up unexpectedly > > $ > > > > it is entirely reproducible, and some googling suggests that this > > represents an error at the *other* end, which in some weird way does > > not support that clone option. that seems strange ... should this > > option work? am i using it incorrectly? > > > > wait, hang on ... i just picked one of django's topic branches at > > random, and this did succeed: > > Yeah i think when you request shallow clone, by default it only gets > one branch (see --single-branch, often 'master'). So when you > specify --shallow-exclude you essentially say 'give me master branch > but exclude everything from master'. > > I should probably make it print a friendlier message than simply > terminateing like that (it's still a guess, I haven't tried it out) this is the first time i've played with this feature, so i'm still working my way through the man page, trying to figure out the various valid combinations for shallow cloning. i notice that the SYNOPSIS for "man git-clone" does not contain all of the supported options (eg., --shallow-exclude is missing, among others). is that deliberate? rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca/dokuwiki Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================
