[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87o80w46du.fsf@meer.lwn.net>
Date: Wed, 20 Apr 2022 00:26:53 -0600
From: Jonathan Corbet <corbet@....net>
To: Bagas Sanjaya <bagasdotme@...il.com>,
Bruno Moreira-Guedes <codeagain@...eagain.dev>,
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 1/2] Docs: Add cpio requirement to changes.rst
Bagas Sanjaya <bagasdotme@...il.com> writes:
> On 4/19/22 21:48, Bruno Moreira-Guedes wrote:
>> diff --git a/Documentation/process/changes.rst b/Documentation/process/changes.rst
>> index a337e8eabfe1..41a44e5f47e6 100644
>> --- a/Documentation/process/changes.rst
>> +++ b/Documentation/process/changes.rst
>> @@ -56,6 +56,7 @@ iptables 1.4.2 iptables -V
>> openssl & libcrypto 1.0.0 openssl version
>> bc 1.06.95 bc --version
>> Sphinx\ [#f1]_ 1.7 sphinx-build --version
>> +cpio any cpio --version
>> ====================== =============== ========================================
>>
>
> You mentioned that **any** version of cpio will work, right?
> Or is there a specific minimum version?
The statement of "any" seems fairly explicit to me. It has been a few
... decades ... since cpio has seen any sort of rapid development; do
you have any reason to think there might be a version in the wild that
would not work?
jon
Powered by blists - more mailing lists