From: Duy Nguyen <pclouds@gmail.com>
To: Steven Evergreen <i.stevenevergreen@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Shallow clone
Date: Tue, 19 Aug 2014 19:01:29 +0700 [thread overview]
Message-ID: <CACsJy8AhaiE0qjQhZfcd6pg5iYy129frvmQOkdR+zrVenuxhWg@mail.gmail.com> (raw)
In-Reply-To: <CAEfjWpHmLXx7Cpyn-Pd+G7VpaXZhFSS741BFKY0kANrh49xt9g@mail.gmail.com>
On Tue, Aug 19, 2014 at 6:11 PM, Steven Evergreen
<i.stevenevergreen@gmail.com> wrote:
> Hi, everyone. I'm trying to perform a shallow clone with visibility of
> all remote branches.
>
> git clone REPO --depth 1 --no-single-branch
>
> is consistently giving me
>
> Cloning into 'REPONAME'...
> fatal: (null) is unknown object
> remote: Total 0 (delta 0), reused 0 (delta 0)
> fatal: recursion detected in die handler
> remote: aborting due to possible repository corruption on the remote side.
> fatal: error in sideband demultiplexer
>
> with 2.0.3 .
>
> Is this command not supported? Have I hit a bug?
Yes it's supported and yes I think you hit a bug. Any chance you can
share this repository? If not, perhaps just SHA-1 so we know what the
commit DAG looks like?
--
Duy
next prev parent reply other threads:[~2014-08-19 12:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEfjWpHhLKpghGRFtzstndk_vYMkLSLAGfXx8agoQmakC-6Otg@mail.gmail.com>
2014-08-19 11:11 ` Fwd: Shallow clone Steven Evergreen
2014-08-19 12:01 ` Duy Nguyen [this message]
2006-11-08 3:21 What's in git.git Junio C Hamano
2006-11-08 4:13 ` David Lang
2006-11-08 16:40 ` Shallow clone [Was Re: What's in git.git ] Aneesh Kumar K.V
2006-11-08 17:59 ` Aneesh Kumar K.V
2006-11-09 4:04 ` Shallow clone Junio C Hamano
2006-11-09 4:17 ` Aneesh Kumar
2006-11-11 13:57 ` Alexandre Julliard
2006-11-12 8:16 ` Junio C Hamano
2006-11-12 17:59 ` Sergey Vlasov
2006-11-12 21:59 ` Junio C Hamano
2006-11-13 5:29 ` Junio C Hamano
2006-11-12 13:12 ` Shallow clone [Was Re: What's in git.git ] Petr Baudis
2006-11-12 20:04 ` Shallow clone Junio C Hamano
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=CACsJy8AhaiE0qjQhZfcd6pg5iYy129frvmQOkdR+zrVenuxhWg@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=i.stevenevergreen@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).