From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 62724@debbugs.gnu.org
Subject: [bug#62724] [PATCH] gnu: mame: Update to 0.253.
Date: Mon, 29 May 2023 23:57:18 +0200 [thread overview]
Message-ID: <87wn0qer7l.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87leh6errh.fsf_-_@gnu.org> ("Ludovic Courtès"'s message of "Mon, 29 May 2023 23:45:22 +0200")
Hello,
Ludovic Courtès <ludo@gnu.org> writes:
> From a quick glance this LGTM. (Per the commit rules you were free to
> go ahead if confident, too.)
Thanks for the review.
I cannot be confident about it because my weak computer cannot compile
mame. As a consequence, I'm waiting for
<https://qa.guix.gnu.org/issue/62724> to tell me that everything is
good, or if something is amiss. But that hasn't happened yet.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2023-05-29 21:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 10:14 [bug#62724] [PATCH] gnu: mame: Update to 0.253 Nicolas Goaziou
2023-04-11 12:53 ` [bug#62724] [PATCH v2] " Nicolas Goaziou
2023-04-12 17:41 ` [bug#62724] [PATCH v3] " Nicolas Goaziou
2023-04-13 11:32 ` [bug#62724] [PATCH v4] " Nicolas Goaziou
2023-04-13 15:37 ` [bug#62724] [PATCH v5] " Nicolas Goaziou
2023-04-14 21:13 ` [bug#62724] [PATCH v6] " Nicolas Goaziou
2023-04-17 11:16 ` [bug#62724] [PATCH v7] " Nicolas Goaziou
2023-04-19 8:53 ` [bug#62724] [PATCH v8] " Nicolas Goaziou
2023-04-20 12:09 ` [bug#62724] [PATCH v9] " Nicolas Goaziou
2023-05-24 8:35 ` [bug#62724] [PATCH v10] gnu: mame: Update to 0.254 Nicolas Goaziou
2023-05-29 21:45 ` [bug#62724] [PATCH] gnu: mame: Update to 0.253 Ludovic Courtès
2023-05-29 21:57 ` Nicolas Goaziou [this message]
2023-06-09 20:43 ` [bug#62724] [PATCH v11] gnu: mame: Update to 0.255 Nicolas Goaziou
2023-06-18 21:22 ` [bug#62724] [PATCH] gnu: mame: Update to 0.253 Ludovic Courtès
2023-06-19 6:19 ` Nicolas Goaziou
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wn0qer7l.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=62724@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.