unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: 44382@debbugs.gnu.org
Subject: bug#44382: Updating the guix package triggers a full Git clone of guix.git
Date: Sun, 29 Nov 2020 22:24:18 -0500	[thread overview]
Message-ID: <87sg8rmsrh.fsf@gmail.com> (raw)
In-Reply-To: <20201105171106.GA9818@jasmine.lan> (Leo Famulari's message of "Thu, 5 Nov 2020 12:11:06 -0500")

Hello,

Leo Famulari <leo@famulari.name> writes:

> On Tue, Nov 03, 2020 at 10:48:25PM +0100, Ludovic Courtès wrote:
>> Weird, what’s the difference between fetch and clone technically?  I
>> believe commit 329dabe13bf98b899b907b45565434c5140804f5 moved to “fetch”
>> precisely so we could do shallow clones.
>
> I don't know. It's definitely weird.

I had researched this before and the option the git server is missing is
uploadpack.allowAnySHA1InWant [0].  Unfortunately last I check in
#savannah their machine (vcs0) is using an older Trisquel stuck with git
v2.11.0, one patch version before when the above feature was introduced
(v2.11.1)!  If I understood correctly, they have a new VM vcs2 but it
needs to be completely setup before they can switch.

Maxim

[0]  https://github.com/git/git/commit/f8edeaa05d8623a9f6dad408237496c51101aad8




  reply	other threads:[~2020-11-30  3:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02  0:50 bug#44382: Updating the guix package triggers a full Git clone of guix.git Leo Famulari
2020-11-02  1:39 ` Leo Famulari
2020-11-03 21:48   ` Ludovic Courtès
2020-11-05 17:11     ` Leo Famulari
2020-11-30  3:24       ` Maxim Cournoyer [this message]
2021-12-29 22:45         ` Leo Famulari
2022-01-02  4:59           ` Maxim Cournoyer

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: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sg8rmsrh.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=44382@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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://git.savannah.gnu.org/cgit/guix.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).