[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <878rrz30d9.fsf@meer.lwn.net>
Date: Wed, 20 Apr 2022 15:34:26 -0600
From: Jonathan Corbet <corbet@....net>
To: Bruno Moreira-Guedes <codeagain@...eagain.dev>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
outreachy@...ts.linux.dev,
Bruno's Patch Watchbox <patch-reply@...eagain.dev>
Subject: Re: [PATCH v2 0/2] Docs: Update information at changes.rst
Bruno Moreira-Guedes <codeagain@...eagain.dev> writes:
> On Wed, Apr 20, 2022 at 03:35:10AM -0600, Jonathan Corbet wrote:
>> Bruno Moreira-Guedes <codeagain@...eagain.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@...eagain.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?
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.
Thanks,
jon
Powered by blists - more mailing lists