From: "Ludovic Courtès" <ludo@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 74892@debbugs.gnu.org
Subject: [bug#74892] [PATCH 7/9] gnu: rust-git2: Switch to ‘git-minimal/pinned’.
Date: Tue, 17 Dec 2024 15:38:59 +0100 [thread overview]
Message-ID: <87r066nzlo.fsf@gnu.org> (raw)
In-Reply-To: <Z18-u_e5sulafV2b@3900XT> (Efraim Flashner's message of "Sun, 15 Dec 2024 22:40:27 +0200")
Efraim Flashner <efraim@flashner.co.il> skribis:
> This can go straight to master.
Thanks. I was considering pushing the whole thing to ‘master’, though
it involves ~3k rebuilds; the other option is to create a temporary
branch and jobset. Thoughts?
Ludo’.
next prev parent reply other threads:[~2024-12-17 14:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 18:14 [bug#74892] [PATCH 0/9] Depending on 'git-minimal/pinned' where appropriate Ludovic Courtès
2024-12-15 18:16 ` [bug#74892] [PATCH 1/9] gnu: python-gitpython: Rewrite to use gexps Ludovic Courtès
2024-12-15 18:16 ` [bug#74892] [PATCH 2/9] gnu: python-gitpython: Switch to ‘git-minimal/pinned’ Ludovic Courtès
2024-12-15 18:16 ` [bug#74892] [PATCH 3/9] gnu: python-gitdb: " Ludovic Courtès
2024-12-15 18:16 ` [bug#74892] [PATCH 4/9] gnu: python-kanon: " Ludovic Courtès
2024-12-15 18:16 ` [bug#74892] [PATCH 5/9] gnu: crun: Switch to ‘git-minimal/pinned' Ludovic Courtès
2024-12-15 18:16 ` [bug#74892] [PATCH 6/9] gnu: podman: Switch to ‘git-minimal/pinned’ Ludovic Courtès
2024-12-15 18:16 ` [bug#74892] [PATCH 7/9] gnu: rust-git2: " Ludovic Courtès
2024-12-15 20:40 ` Efraim Flashner
2024-12-17 14:38 ` Ludovic Courtès [this message]
2024-12-17 17:21 ` Efraim Flashner
2024-12-15 18:16 ` [bug#74892] [PATCH 8/9] gnu: python-reno: " Ludovic Courtès
2024-12-15 18:16 ` [bug#74892] [PATCH 9/9] gnu: pre-commit: " Ludovic Courtès
2024-12-16 15:16 ` [bug#74892] [PATCH 0/9] Depending on 'git-minimal/pinned' where appropriate Greg Hogan
2024-12-17 16:48 ` Sharlatan Hellseher
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=87r066nzlo.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=74892@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/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).