From: zamfofex <zamfofex@twdb.moe>
To: "62917@debbugs.gnu.org" <62917@debbugs.gnu.org>
Subject: bug#62917: [bug report subject correction]
Date: Mon, 17 Apr 2023 21:23:38 -0300 (BRT) [thread overview]
Message-ID: <655414147.1522018.1681777418758@privateemail.com> (raw)
In-Reply-To: <2085439243.1521663.1681776855547@privateemail.com>
Apologies for the noise, but the subject of the email I sent is wrong. It should have been ‘guix shell -CF’ rather than ‘guix shell -CH’.
prev parent reply other threads:[~2023-04-18 0:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 0:14 bug#62917: ‘guix shell -CH’ should be able to contain both GCC and Clang zamfofex
2023-04-18 0:23 ` zamfofex [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=655414147.1522018.1681777418758@privateemail.com \
--to=zamfofex@twdb.moe \
--cc=62917@debbugs.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 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).