[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <OO82gksmp_i249qMnDryWunPoUrSyyFxpxi009wWlytDaijmvalJffHrcPyMNLdfSzcIl5reNfJ2r2SmDVSG8xYXrIIbzc9rw-_bJPMDlag=@emersion.fr>
Date: Mon, 21 Nov 2022 17:06:37 +0000
From: Simon Ser <contact@...rsion.fr>
To: Noralf Trønnes <noralf@...nnes.org>
Cc: dri-devel@...ts.freedesktop.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: git send-email friendly smtp provider anyone?
On Monday, November 21st, 2022 at 18:02, Simon Ser <contact@...rsion.fr> wrote:
> On Monday, November 21st, 2022 at 17:52, Noralf Trønnes noralf@...nnes.org wrote:
>
> > Den 21.11.2022 14.33, skrev Simon Ser:
> >
> > > I think you can apply for a linux.dev mailbox 1.
> >
> > Yeah you're right, I didn't know about that possibility.
> > But it depends on whether or not I can just use their smtp server and
> > keep my current email address. This looks like what's the problem with
> > my current ISP, I need to use the email account I have in their email
> > service (that I've never used) for sending through their smtp server,
> > but I want to send From: another email address.
>
> That's not possible. It breaks DKIM, so your emails will end up in Spam
> folders or be rejected. You need to use the SMTP server tied to your
> email address.
That said, you can send patches from an email address different from
the one in your patches. IOW, you can send patches committed by
<noralf@...nnes.org> from any email account.
The From in the email header won't match the commit, but the very first
line of the patch will hold that information.
Powered by blists - more mailing lists