From: Christoph Hellwig <hch@lst.de>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: git am mailing list compatibility
Date: Fri, 21 Oct 2022 17:16:24 +0200 [thread overview]
Message-ID: <20221021151624.GA30961@lst.de> (raw)
In-Reply-To: <87bkq5be81.fsf@oldenburg.str.redhat.com>
On Fri, Oct 21, 2022 at 01:36:30PM +0200, Florian Weimer via Libc-alpha wrote:
> FYI, I've requested “git am” compatibility here:
>
> Please make libc-alpha mailing list compatible with “git am”
> <https://sourceware.org/bugzilla/show_bug.cgi?id=29713>
FYI, you do not actually need the rewriting for high DMARC reputation.
Take a look at this document that explains the issues very well:
https://people.kernel.org/monsieuricon/subspace-mailing-list-server
next prev parent reply other threads:[~2022-10-21 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 11:36 Florian Weimer
2022-10-21 15:16 ` Christoph Hellwig [this message]
2022-11-01 23:14 ` Mark Wielaard
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=20221021151624.GA30961@lst.de \
--to=hch@lst.de \
--cc=fweimer@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).