From: 🅰🅼🅰🆉🅾🅽 <mailscureuspsinfo56623641738@gaskanteros.com>
To: gcc-help@gcc.gnu.org
Subject: =?UTF-8?B?W0HigIzigIzigIzigIzigIzigIzigIxtYeKAjOKAjOKAjOKAjOKAjOKAjOKAjHrigIzigIzigIzigIzigIzigIzigIxvbi5j4oCM4oCM4oCM4oCM4oCM4oCM4oCMb21dIC0g?= =?UTF-8?B?W1JlbWluZGVyXSA6IFNvbWUgZGV2aWNlIGhhcyBiZWVuIHNpZ24taW4gb24geW91ciBBbWHigIzigIzigIzigIzigIx6b24gSeKAjOKAjOKAjOKAjOKAjEQsIG5lZWRlZCBhY3Rpb24gcmVxdWlyZWQ=?=
Date: Sat, 20 Jan 2024 17:01:16 +0000 [thread overview]
Message-ID: <c6cf1795-ce1b-16f0-17b9-d22c857fa80e@gaskanteros.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 10 bytes --]
vKrSyyJi2Q
next reply other threads:[~2024-01-20 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 17:01 🅰🅼🅰🆉🅾🅽 [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-20 16:57 🅰🅼🅰🆉🅾🅽
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=c6cf1795-ce1b-16f0-17b9-d22c857fa80e@gaskanteros.com \
--to=mailscureuspsinfo56623641738@gaskanteros.com \
--cc=gcc-help@gcc.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.
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).