From: Jeff King <peff@peff.net>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Mike Edgar <adgar@google.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] clone: check if server supports shallow clones
Date: Thu, 11 Jun 2015 10:32:07 -0400 [thread overview]
Message-ID: <20150611143204.GA3343@peff.net> (raw)
In-Reply-To: <CACsJy8CiwiWgf2CarNNN5NgN7QbRB8oxGMmxF+VX8T=ZV2M1ow@mail.gmail.com>
On Thu, Jun 11, 2015 at 08:02:33PM +0700, Duy Nguyen wrote:
> > I see that do_fetch_pack checks server_supports("shallow"). Is that
> > enough to cover all fetch cases? And if it is, why does it not cover the
> > matching clone cases?
>
> I think this replacement check would do
>
> if ((args->depth > 0 || is_repository_shallow()) && !server_supports("shallow"))
> die("Server does not support shallow clients");
Oh, indeed, there is the depth flag I was looking for. :)
And from some rudimentary testing, I believe that:
git init
git fetch --depth=1 ...
is currently broken in the same way as clone (we are not shallow yet, so
it does not complain when the server does not support it). I think the
patch above fixes both that and the clone case.
Of course it's hard to add to the test suite, since we do not have a way
of hitting a server that does not understand shallow (I simply fudged
server_supports() to return false on the client).
-Peff
next prev parent reply other threads:[~2015-06-11 14:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 18:35 [PATCH] clone: check if server supports shallow clones Mike Edgar
2015-06-10 19:05 ` Jeff King
2015-06-10 20:25 ` Michael Edgar
2015-06-10 20:56 ` Jeff King
2015-06-11 13:02 ` Duy Nguyen
2015-06-11 14:32 ` Jeff King [this message]
2015-06-11 18:18 ` Michael Edgar
2015-06-11 20:44 ` Junio C Hamano
2015-06-17 11:48 ` [PATCH v2] fetch-pack: check for shallow if depth given Mike Edgar
2015-06-17 17:00 ` Jeff King
2015-06-17 16:35 ` [PATCH] clone: check if server supports shallow clones Junio C Hamano
2015-06-17 16:59 ` Jeff King
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=20150611143204.GA3343@peff.net \
--to=peff@peff.net \
--cc=adgar@google.com \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.