From: Bruno Moreira-Guedes <codeagain@codeagain.dev>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
outreachy@lists.linux.dev,
Bruno's Patch Watchbox <patch-reply@codeagain.dev>
Subject: Re: [PATCH v2 0/2] Docs: Update information at changes.rst
Date: Wed, 20 Apr 2022 14:27:31 -0300 [thread overview]
Message-ID: <20220420172731.ru7kfrdkmprybtu7@AN5Bruno> (raw)
In-Reply-To: <8735i83xo1.fsf@meer.lwn.net>
[-- Attachment #1: Type: text/plain, Size: 585 bytes --]
On Wed, Apr 20, 2022 at 03:35:10AM -0600, Jonathan Corbet wrote:
> Bruno Moreira-Guedes <codeagain@codeagain.dev> writes:
> >
> > The PATCH 1/2 fixes the missing cpio requirement, while PATCH 2/2 fixes
> > the kernel version reference.
> >
> > Signed-off-by: Bruno Moreira-Guedes <codeagain@codeagain.dev>
>
> Patches applied, thanks.
Thanks, Jon! I have also been thinking whether this filename
('changes.rst') is a good description of the file contents. Do you think
renaming it to something like 'requirements.rst' and updating its
references would be a good patch?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-04-20 17:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 14:47 [PATCH v2 0/2] Docs: Update information at changes.rst Bruno Moreira-Guedes
2022-04-19 14:48 ` [PATCH v2 1/2] Docs: Add cpio requirement to changes.rst Bruno Moreira-Guedes
2022-04-20 6:07 ` Bagas Sanjaya
2022-04-20 6:26 ` Jonathan Corbet
2022-04-19 14:48 ` [PATCH v2 2/2] Docs: Replace version by 'current' in changes.rst Bruno Moreira-Guedes
2022-04-20 9:35 ` [PATCH v2 0/2] Docs: Update information at changes.rst Jonathan Corbet
2022-04-20 17:27 ` Bruno Moreira-Guedes [this message]
2022-04-20 21:34 ` Jonathan Corbet
2022-04-21 7:50 ` Bagas Sanjaya
2022-04-21 8:09 ` Jonathan Corbet
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=20220420172731.ru7kfrdkmprybtu7@AN5Bruno \
--to=codeagain@codeagain.dev \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy@lists.linux.dev \
--cc=patch-reply@codeagain.dev \
/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.