From: Yodel Eldar <yodel.eldar@gmail.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: gdb-patches@sourceware.org, Simon Marchi <simark@simark.ca>,
Yodel Eldar <yodel.eldar@gmail.com>
Subject: Re: [PATCH 1/2] gdb/alpha: Add target description support
Date: Thu, 3 Jul 2025 11:49:11 -0500 [thread overview]
Message-ID: <bfd0f807-c989-4599-b34a-6f28299569a6@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2507022156101.56608@angie.orcam.me.uk>
On 7/2/25 4:12 PM, Maciej W. Rozycki wrote:
> On Wed, 2 Jul 2025, Yodel Eldar wrote:
>
>> Hi, Maciej! For unknown reasons, your emails are not appearing in my
>> inbox (or even the Spam folder) on any of the email clients I use.
>> Fortunately, I'm able to import them from the gdb-patches public inbox,
>> but I had not seen your email about the newline until after I sent my
>> previous email.
> Indeed a while ago GMail started refusing e-mail originating from my mail
> server owing to the lack of annotation they require. You'll still receive
> copies via the mailing list as long as you're subscribed, which I take it
> you're not.
>
> Apologies for the inconvenience, but I'm not going to do anything about
> it. E-mail is analogous to post and just as anyone can post anything
> through my letter box I expect all recipients to accept all the e-mail I
> send and not just messages specially marked on the envelope. Just as it
> has been through 30 years I've been using this way to communicate.
>
> Maciej
On a second reading of my previous email, it does look like I was
complaining about having to import from the public inbox, but that was
not my intention; I meant to clarify how I was able to respond despite
not having a copy of your emails in my inbox. I loathe the thought of
having elicited an apology from a veteran developer such as yourself for
whom I have immense respect and gratitude as there is nothing that calls
for an apology in my view, and I certainly would neither ask nor expect
you to modify your server/DNS configuration to accommodate for my or
GMail's security preferences/requirements.
I have been experimenting with different configurations of the public
email based patch workflow in the following order:
1. Individual delivery subscription
2. NNTP
3. Digest subscription
4. Atom Feed (current setup)
Next will probably be a dedicated, self-managed email server where I will
be able to whitelist email addresses/domains at will.
Thanks for sharing your perspective on how emails should operate,
especially in the context of a public email based workflow; it will help
me fine-tune my server configuration in the near future.
Yodel
next prev parent reply other threads:[~2025-07-03 17:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 15:12 [PATCH 0/2] gdb/alpha: Add target description support and fpcr flags Yodel Eldar
2025-05-26 15:12 ` [PATCH 1/2] gdb/alpha: Add target description support Yodel Eldar
2025-05-26 16:13 ` Eli Zaretskii
2025-05-26 17:14 ` Yodel
2025-06-03 18:49 ` Simon Marchi
2025-06-04 13:44 ` Yodel Eldar
2025-06-04 14:49 ` Maciej W. Rozycki
2025-06-04 17:29 ` Yodel Eldar
2025-06-12 19:29 ` Yodel Eldar
2025-06-12 20:30 ` Simon Marchi
2025-06-12 20:33 ` Simon Marchi
2025-06-12 22:07 ` Yodel Eldar
2025-06-13 14:34 ` Simon Marchi
2025-06-30 0:08 ` Yodel Eldar
2025-07-02 17:14 ` Simon Marchi
2025-07-02 18:51 ` Yodel Eldar
2025-07-02 18:53 ` Maciej W. Rozycki
2025-07-02 19:02 ` Simon Marchi
2025-07-02 19:21 ` Maciej W. Rozycki
2025-07-02 20:52 ` Yodel Eldar
2025-07-02 21:12 ` Maciej W. Rozycki
2025-07-03 16:49 ` Yodel Eldar [this message]
2025-07-03 16:02 ` Simon Marchi
2025-07-02 18:48 ` Maciej W. Rozycki
2025-05-26 15:12 ` [PATCH 2/2] gdb/alpha: Redefine fpcr with fpcr_flags type Yodel Eldar
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=bfd0f807-c989-4599-b34a-6f28299569a6@gmail.com \
--to=yodel.eldar@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@orcam.me.uk \
--cc=simark@simark.ca \
/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