riorities
here. From my perspective, the problem is getting the patch into a git
repo with the right author name. But patchwork may want to make the
distinction between author and sender.
Yes, I was referring to the git am case, not the Patchwork case.
--
Andrew Donnellan OzLabs, ADL Can
On 11/10/19 3:36 pm, Andrew Donnellan wrote:
It would be nice if Mailman could adopt X-Original-Sender too. As it is,
(which I have gone ahead and reported as
https://gitlab.com/mailman/mailman/issues/641)
--
Andrew Donnellan OzLabs, ADL Canberra
a...@linux.ibm.com
For the Patchwork use case, I'm quite okay with accepting the risk of
using Reply-To, as the alternative is worse, the corner cases are rare,
and ultimately a maintainer can still fix the odd stuff-up before
applying the patch.
--
Andrew Donnellan OzLabs, ADL Canberra
a..
bust - but OTOH there's always a long tail of users
stuck on old versions of git for whatever reason and having some logic
to detect DMARC munging may thus still be useful.
--
Andrew Donnellan OzLabs, ADL Canberra
a...@linux.ibm.com IBM Australia Limited
bably just change it?
--
Andrew Donnellan OzLabs, ADL Canberra
a...@linux.ibm.com IBM Australia Limited
r than
+ application.
Perhaps mention the phrase "Request For Comment" for the benefit of
those who aren't familiar (which admittedly, among users of
git-format-patch, are probably rather few, but still).
--
Andrew Donnellan OzLabs, ADL Canberra
andrew.donnel...@au1.ibm.com IBM Australia Limited
6 matches
Mail list logo