From: "Shawn O. Pearce" <spearce@spearce.org>
To: Christian Schlotter <schlotter@users.sourceforge.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-clone: Sync documentation to usage note.
Date: Thu, 15 Feb 2007 17:38:02 -0500 [thread overview]
Message-ID: <20070215223802.GA27992@spearce.org> (raw)
In-Reply-To: <117157763494-git-send-email-schlotter@users.sourceforge.net>
Christian Schlotter <schlotter@users.sourceforge.net> wrote:
> Please note that I was not able to test the new shallow clone feature, as
> both
> git clone --depth=5 git://git2.kernel.org/pub/scm/git/git.git
> and
> git clone --depth 5 git://git2.kernel.org/pub/scm/git/git.git
> do not seem to work. The former correctly produces the usage note, while
> the latter prints
>
> Initialized empty Git repository in /home/cs/tmp2/git/.git/
> fatal: read error (Connection reset by peer)
> fetch-pack from 'git://git2.kernel.org/pub/scm/git/git.git' failed.
>
> Is this a problem on my end?
Sort of. ;-)
The server side must also support shallow clone. I don't think
the server on kernel.org has been upgraded yet to a version which
supports that feature, so you cannot shallow clone from there.
--
Shawn.
prev parent reply other threads:[~2007-02-15 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 22:13 [PATCH] git-clone: Sync documentation to usage note Christian Schlotter
2007-02-15 22:38 ` Shawn O. Pearce [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070215223802.GA27992@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=schlotter@users.sourceforge.net \
/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.
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 NNTP newsgroup(s).