From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Chuck Lever <cel@kernel.org>,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
Jeff Layton <jlayton@kernel.org>
Subject: Re: [GIT PULL] NFSD changes for v6.16
Date: Wed, 28 May 2025 16:18:08 -0400 [thread overview]
Message-ID: <20250528-wise-platinum-pony-ea6f62@lemur> (raw)
In-Reply-To: <CAHk-=wggC6PP9ZNwKY7sEzdsC7h8qySA7pjqAchrYowniADUQg@mail.gmail.com>
On Wed, May 28, 2025 at 12:38:58PM -0700, Linus Torvalds wrote:
> Can you fix your kernel.org email sending setup so that you have a
> real name, not just your login name?
>
> This is not your fault, btw. I think the kernel.org email sending
> documentation is actively misleading and wrong, with
>
> https://korg.docs.kernel.org/mail.html
>
> and the 'getsmtppass' output saying that you should do things like
>
> from = "[username]@kernel.org"
>
> in your git config (or mutt settings), like you were some kind of bot
> that didn't have an actual name.
>
> Konstantin, can we please get the kernel.org documentation and
> getsmtpass output fixed? We had somebody else who also ended up being
> nameless (Ingo, I think) due to following the documentation a bit too
> slavishly.
I've updated it to say:
from = "Your Name <[username]@kernel.org>"
So, if you receive mail from a bunch of people called "Your Name", at least
you'll know that they are reading the documentation (and still following it a
bit too slavishly). :)
-K
next prev parent reply other threads:[~2025-05-28 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 14:17 [GIT PULL] NFSD changes for v6.16 cel
2025-05-28 19:38 ` Linus Torvalds
2025-05-28 19:44 ` Chuck Lever
2025-05-28 20:18 ` Konstantin Ryabitsev [this message]
2025-05-28 20:35 ` Linus Torvalds
2025-05-28 19:44 ` pr-tracker-bot
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=20250528-wise-platinum-pony-ea6f62@lemur \
--to=konstantin@linuxfoundation.org \
--cc=cel@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.