From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Git Mailing list <git@vger.kernel.org>
Subject: "git clone --shallow-exclude ...", fatal: the remote end hung up unexpectedly
Date: Fri, 15 Mar 2019 08:14:18 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.1903150809070.26709@localhost.localdomain> (raw)
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:
$ git clone --shallow-exclude=stable/2.0.x https://github.com/django/django.git
Cloning into 'django'...
remote: Enumerating objects: 33112, done.
remote: Counting objects: 100% (33112/33112), done.
... etc etc ...
$
but all this gave me was the master branch. i clearly don't understand
what this option is supposed to do.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2019-03-15 12:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 12:14 Robert P. J. Day [this message]
2019-03-15 12:28 ` "git clone --shallow-exclude ...", fatal: the remote end hung up unexpectedly Duy Nguyen
2019-03-15 13:19 ` Robert P. J. Day
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.1903150809070.26709@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=git@vger.kernel.org \
/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).