From: Marius Bakke <marius@gnu.org>
To: Greg Hogan <code@greghogan.com>, 57344-done@debbugs.gnu.org
Cc: Greg Hogan <code@greghogan.com>
Subject: bug#57344: [PATCH] gnu: gcc-12: Update to 12.2.0.
Date: Sat, 27 Aug 2022 00:05:45 +0200 [thread overview]
Message-ID: <87lerafyo6.fsf@gnu.org> (raw)
In-Reply-To: <397aa22739310fd3baae610ef8e95becdefaf9cb.1661192693.git.code@greghogan.com>
[-- Attachment #1: Type: text/plain, Size: 113 bytes --]
Greg Hogan <code@greghogan.com> skriver:
> * gnu/packages/gcc.scm (gcc-12): Update to 12.2.0.
Applied, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
prev parent reply other threads:[~2022-08-26 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 18:26 [bug#57344] [PATCH] gnu: gcc-12: Update to 12.2.0 Greg Hogan
2022-08-26 22:05 ` Marius Bakke [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=87lerafyo6.fsf@gnu.org \
--to=marius@gnu.org \
--cc=57344-done@debbugs.gnu.org \
--cc=code@greghogan.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).