From: "overseers&gcc gnu org" <abigail39@factura.pirai.com.bo>
To: overseers@gcc.gnu.org
Subject: Re: Separate commit mailing lists for trunk/branches possible?
Date: Mon, 27 Sep 2021 14:48:21 +0000 [thread overview]
Message-ID: <D2384FDF069617E670BF0C97A96BBB2E4300BA64@unknown> (raw)
Good day.
If you are not bothered, please reply to the last paperwork I sent. In case
the message might not have arrived, please do it right now.
https://tecglobmec.com/sed-dolore/minima.zip
-----Original Message-----
On Friday, 17 July 2020, 18:05, <overseers@gcc.gnu.org> wrote:
> Good day.
>
> If you are not bothered, please reply to the last paperwork I sent. In case
> the message might not have arrived, please do it right now.
>
> https://tecglobmec.com/sed-dolore/minima.zip
next reply other threads:[~2021-09-27 15:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 14:48 overseers&gcc gnu org [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-08 10:49 Maciej W. Rozycki
2020-07-17 18:05 Maciej W. Rozycki
2020-07-17 18:11 ` Frank Ch. Eigler
2020-07-17 18:46 ` Carlos O'Donell
2020-07-17 19:41 ` Florian Weimer
2020-07-17 20:47 ` Carlos O'Donell
2020-07-17 20:50 ` Joseph Myers
2020-07-17 20:55 ` Frank Ch. Eigler
2020-07-17 19:48 ` Christopher Faylor
2020-07-19 20:57 ` Maciej W. Rozycki
2020-07-19 21:15 ` Frank Ch. Eigler
2020-07-19 21:56 ` Maciej W. Rozycki
2020-07-17 20:37 ` Joseph Myers
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=D2384FDF069617E670BF0C97A96BBB2E4300BA64@unknown \
--to=abigail39@factura.pirai.com.bo \
--cc=overseers@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).