From: Jonathan Corbet <corbet@lwn.net>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
linux-doc@vger.kernel.org, device@lanana.org, unicode@lanana.org,
"H . Peter Anvin" <hpa@zytor.com>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: [PATCH 0/2] Updating information on lanana.org
Date: Tue, 14 Mar 2023 12:30:42 -0600 [thread overview]
Message-ID: <87edprrxrh.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230307144000.29539-1-lukas.bulwahn@gmail.com>
Lukas Bulwahn <lukas.bulwahn@gmail.com> writes:
> Dear Jon,
>
> please pick these two changes that update information in MAINTAINERS and
> the kernel documentation on the actual state of lanana.org.
Done, applied.
Thanks,
jon
prev parent reply other threads:[~2023-03-14 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 14:39 [PATCH 0/2] Updating information on lanana.org Lukas Bulwahn
2023-03-07 14:39 ` [PATCH 1/2] MAINTAINERS: remove historic section DEVICE NUMBER REGISTRY Lukas Bulwahn
2023-03-07 14:40 ` [PATCH 2/2] docs: admin: unicode: update information on state of lanana.org document Lukas Bulwahn
2023-03-14 18:30 ` Jonathan Corbet [this message]
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=87edprrxrh.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=device@lanana.org \
--cc=hpa@zytor.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=unicode@lanana.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