From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 30428@debbugs.gnu.org
Subject: bug#30428: guix git-fetch doesn't specify "--depth 1" - git clone clones a lot without any use
Date: Wed, 14 Feb 2018 14:58:55 +0100 [thread overview]
Message-ID: <87fu63sme8.fsf@gnu.org> (raw)
In-Reply-To: <20180212235950.4638aad6@scratchpost.org> (Danny Milosavljevic's message of "Mon, 12 Feb 2018 23:59:50 +0100")
Hello,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> On Mon, 12 Feb 2018 10:09:39 -0500
> Leo Famulari <leo@famulari.name> wrote:
>
>> I think it's worth adding, but as an option, because there are Git
>> server implementations, like JGit, that don't support shallow cloning.
>
> Thanks for that! I didn't consider that before...
>
> Possible patch (do you know such servers and can test whether they still work?):
I think it’s a great idea. FWIW, Andy proposed something along these
lines, but the idea was to use shallow clones for tags only because in
other cases it might not work (?):
https://lists.gnu.org/archive/html/guix-devel/2015-08/msg00258.html
It got stuck on a minor issue: the patch added a ‘tag’ field to
‘git-reference’, which changed the API, and I suggested making things
slightly differently:
https://lists.gnu.org/archive/html/guix-devel/2015-08/msg00558.html
Would you like to see if both patches could be merged?
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-02-14 14:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 0:16 bug#30428: guix git-fetch doesn't specify "--depth 1" - git clone clones a lot without any use Danny Milosavljevic
2018-02-12 15:09 ` Leo Famulari
2018-02-12 22:59 ` Danny Milosavljevic
2018-02-13 1:28 ` Leo Famulari
2018-02-13 14:22 ` Leo Famulari
2018-02-13 17:08 ` Marius Bakke
2018-02-13 18:08 ` Leo Famulari
2018-02-13 17:09 ` Marius Bakke
2018-02-14 13:58 ` Ludovic Courtès [this message]
2018-02-18 13:38 ` Danny Milosavljevic
2018-02-18 13:53 ` Ludovic Courtès
2020-03-22 20:48 ` Leo Famulari
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=87fu63sme8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30428@debbugs.gnu.org \
--cc=dannym@scratchpost.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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.