From: Mayank Gite <drapl0n.kernel@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Paul Moore <paul@paul-moore.com>,
Serge Hallyn <sergeh@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-security-module@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: fix typo and formattting in security/credentials.rst
Date: Thu, 7 May 2026 15:35:13 -0400 [thread overview]
Message-ID: <afzoL4RJk3po1Hwy@drapl0n.kernel> (raw)
In-Reply-To: <87pl378417.fsf@trenco.lwn.net>
On Thu, May 07, 2026 at 12:31:48PM -0600, Jonathan Corbet wrote:
> John Doe <drapl0n.kernel@gmail.com> writes:
>
> > Thank you for the feedback and acknowledgment. I thought that since my
> > earlier patch was invalid/corrupted, I should submit a new one rather than
> > version 2.
> >
> > I understand the procedure now and will ensure that future revisions follow
> > the guidelines.
>
> Along those lines, seeing multiple names associated with the same email
> account is a bit disconcerting. We are not generally interested in
> taking patches submitted under pseudonyms...
While configuring mutt, I forgot to change the default placeholder value
for the "realname" variable, resulting in an inconsistent sender name.
I have corrected the configuration and verified that my environment is
now set up appropriately.
Sorry for the confusion.
Mayank
next prev parent reply other threads:[~2026-05-07 19:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 22:59 [PATCH] Documentation: fix typo and formattting in security/credentials.rst Mayank Gite
2026-05-07 0:36 ` Randy Dunlap
2026-05-07 17:48 ` John Doe
2026-05-07 18:31 ` Jonathan Corbet
2026-05-07 19:35 ` Mayank Gite [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-06 5:49 Mayank Gite
2026-05-06 17:31 ` Randy Dunlap
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=afzoL4RJk3po1Hwy@drapl0n.kernel \
--to=drapl0n.kernel@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=rdunlap@infradead.org \
--cc=sergeh@kernel.org \
--cc=skhan@linuxfoundation.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