From: "<Jedna Paula> thereisnotimeforsleep1@gmail.com" <parceiros@crassuscertificados.com.br>
To: "" <gcc-patches@gcc.gnu.org>
Subject: RE: gcc-patches@gcc.gnu.org
Date: Tue, 14 Jun 2022 05:35:01 -0300 [thread overview]
Message-ID: <d6fd1e2c-06e8-4e5f-c796-e3b32af77e88@crassuscertificados.com.br> (raw)
[-- Attachment #1: DATA_7226226.zip --]
[-- Type: application/x-zip-compressed, Size: 35856 bytes --]
next reply other threads:[~2022-06-14 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 8:35 <Jedna Paula> thereisnotimeforsleep1@gmail.com [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-23 2:15 gcc-patches@gcc.gnu.org <Jedna Paula> thereisnotimeforsleep1@gmail.com
2004-03-20 18:20 gcc-patches@gcc.gnu.org Ulrich Weigand
2003-08-27 10:51 gcc-patches@gcc.gnu.org Esteban Barrios
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=d6fd1e2c-06e8-4e5f-c796-e3b32af77e88@crassuscertificados.com.br \
--to=parceiros@crassuscertificados.com.br \
--cc=gcc-patches@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).