From: Jack Hill <jackhill@jackhill.us>
To: Wilke Schwiedop <wilke.schwiedop@agfa.com>
Cc: 66887@debbugs.gnu.org
Subject: [bug#66887] [PATCH v2 0/3] resending catatonit patches for QA
Date: Wed, 8 Nov 2023 12:22:53 -0500 (EST) [thread overview]
Message-ID: <df488964-c300-85d7-52e1-bf2768effa16@jackhill.us> (raw)
In-Reply-To: <DB9P190MB1985EACDCB1AD8D10E7807F19EA7A@DB9P190MB1985.EURP190.PROD.OUTLOOK.COM>
Hi Guix,
I'm resending the catatonit series because it wasn't picked up properly by
patchwork/QA the first time. I haven't done a review of the patches, but
it does look like the commit messages will need to be re-worded to fit our
style.
Best,
Jack
Wilke Schwiedop (3):
gnu: Add catatonit.
gnu: podman: Use catatonit.
remove outdated comment
gnu/packages/containers.scm | 42 ++++++++++++++++++++++++++++++-------
1 file changed, 35 insertions(+), 7 deletions(-)
base-commit: 00fd6895322d0b1fd774e79494cfcad721b50b8d
--
2.41.0
next prev parent reply other threads:[~2023-11-08 17:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 18:23 [bug#66887] Subject: [PATCH 0/3] catatonit for podman Wilke Schwiedop via Guix-patches via
2023-11-01 18:45 ` [bug#66887] Subject: [PATCH 1/3] gnu: Add catatonit Wilke Schwiedop via Guix-patches via
2023-11-01 18:47 ` [bug#66887] Subject: [PATCH 2/3] gnu: podman: Use catatonit Wilke Schwiedop via Guix-patches via
2023-11-01 18:47 ` [bug#66887] Subject: [PATCH 3/3] remove outdated comment Wilke Schwiedop via Guix-patches via
2023-11-08 17:22 ` Jack Hill [this message]
2023-11-08 17:24 ` [bug#66887] [PATCH v2 1/3] gnu: Add catatonit Jack Hill
2023-11-08 17:24 ` [bug#66887] [PATCH v2 2/3] gnu: podman: Use catatonit Jack Hill
2023-11-08 17:24 ` [bug#66887] [PATCH v2 3/3] remove outdated comment Jack Hill
2023-11-19 11:45 ` [bug#66887] [PATCH v2 0/3] resending catatonit patches for QA Wilke Schwiedop via Guix-patches via
2024-04-01 15:23 ` [bug#66887] Superceded by #70112 Wilke Schwiedop via Guix-patches via
2024-05-22 14:01 ` bug#66887: " Simon Tournier
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=df488964-c300-85d7-52e1-bf2768effa16@jackhill.us \
--to=jackhill@jackhill.us \
--cc=66887@debbugs.gnu.org \
--cc=wilke.schwiedop@agfa.com \
/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).