Thread (17 messages) 17 messages, 12 authors, 2022-01-09

Re: Review process improvements

flat view

From: Fabian Stelzer <hidden>
Date: 2021-12-22 13:07:49
Also in: workflows

On 22.12.2021 04:26, Ævar Arnfjörð Bjarmason wrote:
On Fri, Dec 17 2021, Konstantin Ryabitsev wrote:
quoted
[...]
   - on the receiving end, the patches will be written to a dedicated
     lore.kernel.org feed *as-is*, but also sent to the recipients after doing
     the usual From/Reply-To substitution and moving the original From into
     the in-body git headers (i.e. same as GGG does).
That GGG does this is one reason I haven't considered using it. It
breaks all sorts of E-Mail workflow assumptions from polluting the
address book for every person who uses it, to any "from:<addr>" search
needing special consideration etc.
I agree that this is a very annoying side-effect of GGG.
Of course you'd need authentication etc, but is there a reason for why
such tooling can't work more like an SMTP relay and less like GGG which
(for some reason) insists on taking over the "From" header?
I think SPF/DMARC spam filtering will prevent tools like GGG to do this any other way. For GGG to be able to send with your From: you'd either need to give it access to your smtp credentials or configure your whole domain to allow GGG mail servers (basically github) to send email for it. I think both options are not really something you'd want.
I think in its case it's because it wanted to mirror all the discussion
to GitHub. But presumably a ML-native tool won't have that problem (and
presumably GGG could do the same mirroring by following the ML after
submission).
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help