git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Git Mailing list <git@vger.kernel.org>
Subject: Re: "git clone --shallow-exclude ...", fatal: the remote end hung up unexpectedly
Date: Fri, 15 Mar 2019 09:19:26 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.21.1903150917360.27423@localhost.localdomain> (raw)
In-Reply-To: <CACsJy8DVRJ4DG6PEkFuzytOQJ7RX6GMaHd4BRQTR9N7Y9V6fqQ@mail.gmail.com>

On Fri, 15 Mar 2019, Duy Nguyen wrote:

> On Fri, Mar 15, 2019 at 7:17 PM Robert P. J. Day <rpjday@crashcourse.ca> 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
========================================================================

  reply	other threads:[~2019-03-15 13:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-15 12:14 "git clone --shallow-exclude ...", fatal: the remote end hung up unexpectedly Robert P. J. Day
2019-03-15 12:28 ` Duy Nguyen
2019-03-15 13:19   ` Robert P. J. Day [this message]
2019-03-15 13:41     ` Duy Nguyen
2019-03-15 14:31       ` Robert P. J. Day
2019-03-16  3:43         ` Duy Nguyen
2019-03-16 12:15           ` Robert P. J. Day

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.21.1903150917360.27423@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=git@vger.kernel.org \
    --cc=pclouds@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).