From: Mark Wielaard <mark@klomp.org>
To: Carlos O'Donell <carlos@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Testing sending from client that always creates HTML email.
Date: Fri, 5 Apr 2024 22:02:56 +0200 [thread overview]
Message-ID: <20240405200256.GI1292@gnu.wildebeest.org> (raw)
In-Reply-To: <CAEMqeSptxRpS0yF-EK=QvsES+Av7fsfbsRXXZkNtnKL-CoKaOQ@mail.gmail.com>
Hi Carlos,
On Fri, Apr 05, 2024 at 02:51:40PM -0400, Carlos O'Donell wrote:
> Testing sending.
Maybe I can explain the mailinglist setup, so you don't need to sent
all these test emails. The setup was discussed last year on this list
and can also be found in bugzilla:
https://inbox.sourceware.org/20230906184940.GA19396@gnu.wildebeest.org/
https://sourceware.org/bugzilla/show_bug.cgi?id=29713
Hope that helps. If you do have questions or want help with the
mailinglist please feel free to reach out:
https://sourceware.org/mission.html#organization
Cheers,
Mark
prev parent reply other threads:[~2024-04-05 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 18:51 Testing sending from client that always creates HTML email Carlos O'Donell
2024-04-05 20:02 ` Mark Wielaard [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://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240405200256.GI1292@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.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).