From: "Ludovic Courtès" <ludo@gnu.org>
To: unmush <unmush@proton.me>
Cc: 74609@debbugs.gnu.org
Subject: [bug#74609] [PATCH] Adding a fully-bootstrapped mono
Date: Fri, 13 Dec 2024 22:22:46 +0100 [thread overview]
Message-ID: <87wmg3z3a1.fsf@gnu.org> (raw)
In-Reply-To: <iMoekcfwEfCp2uLTWzr-P2_OVyzTF-420AoXae5W6GK2kP5NvueOXBRzAIJBRN2U0c7Sl0HUzUy8eKWNuTs2uaiapCUkJUo5Ng9ahfsfGZ8=@proton.me> (unmush@proton.me's message of "Fri, 29 Nov 2024 15:05:09 +0000")
unmush <unmush@proton.me> skribis:
> First, github dropped support for the git:// protocol in 2021, so
> recursive clones won't work now. This means I have to explicitly list
> out every submodule, its commit, and its sha256 hash, for every mono
> version until they switched to using http or https. mono-2.11.4 has
> only 4 submodules, but that doesn't last for long: by mono-4.9.0 it has
> 14 submodules. A significant portion of these patches is just listing
> these submodules and their hashes. It's a bit annoying.
As I read this, I realize that ‘git-fetch-with-fallback’ (used by
‘git-fetch’ for origins) won’t actually fall back to Software Heritage
for just submodules. It’s all or nothing.
So the SWH fallback didn’t help you at all, right?
In an ideal world, it would have kicked in automatically.
Ludo’.
prev parent reply other threads:[~2024-12-13 21:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 15:05 [bug#74609] [PATCH] Adding a fully-bootstrapped mono unmush via Guix-patches via
2024-12-05 6:21 ` Aaron Covrig via Guix-patches via
2024-12-05 22:07 ` Richard Sent
2024-12-13 7:47 ` Ludovic Courtès
2024-12-13 12:13 ` Janneke Nieuwenhuizen
2024-12-13 21:22 ` Ludovic Courtès [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
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=87wmg3z3a1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=74609@debbugs.gnu.org \
--cc=unmush@proton.me \
/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).