From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
Bruno Moreira-Guedes <codeagain@codeagain.dev>
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: Thu, 21 Apr 2022 14:50:24 +0700 [thread overview]
Message-ID: <2f4c72d2-4669-4217-f322-9d4f34c3053e@gmail.com> (raw)
In-Reply-To: <878rrz30d9.fsf@meer.lwn.net>
On 4/21/22 04:34, Jonathan Corbet wrote:
>> 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?
>
> It's best not to rename things unnecessarily, especially relatively
> well-known files that a lot of people expect to find in a specific
> place. We've done a lot of renaming over the last few years, but this
> is one I might let slide for now.
>
Did you mean the rename will be benefical?
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-04-21 7:50 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
2022-04-20 21:34 ` Jonathan Corbet
2022-04-21 7:50 ` Bagas Sanjaya [this message]
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=2f4c72d2-4669-4217-f322-9d4f34c3053e@gmail.com \
--to=bagasdotme@gmail.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).