GNU bug report logs - #76503
[GCD] Migrating repositories, issues, and patches to Codeberg

Previous Next

Full log

View this message in rfc822 format

From: 45mg <45mg.writes <at> gmail.com>
To: Arun Isaac <arunisaac <at> systemreboot.net>, Leo Famulari <leo <at> famulari.name>
Cc: 76503 <at> debbugs.gnu.org, Ricardo Wurmus <rekado <at> elephly.net>, Ludovic Courtès <ludo <at> gnu.org>, Christopher Baines <guix <at> cbaines.net>, Benjamin Slade <slade <at> lambda-y.net>
Subject: [bug#76503] [GCD] Migrating repositories, issues, and patches to Codeberg
Date: Wed, 26 Feb 2025 10:33:10 +0000

Arun Isaac <arunisaac <at> systemreboot.net> writes:

>> Like I've said several times in this discussion so far, we should look
>> into the state of the art of shallow cloning. It might be efficient
>> enough on the server-side these days to be the smart move. I agree that
>> downloading 1 GB in this context is bad.
>
> Good idea. I don't know if our `guix authenticate' security model would
> still work with a shallow clone. But, it's worth exploring.

If shallow cloning leads to a truncated commit history that doesn't
include the current introductory commit
(9edb3f66fd807b096b48283debdcddccfea34bad), then you'd need to specify a
later commit as the introductory commit during the first run of `guix
git authenticate`. Other than that, it should still work.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.