From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Bruno Moreira-Guedes <codeagain@codeagain.dev>,
Jonathan Corbet <corbet@lwn.net>,
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 1/2] Docs: Add cpio requirement to changes.rst
Date: Wed, 20 Apr 2022 13:07:27 +0700 [thread overview]
Message-ID: <ed6cd79c-6a1d-8299-c90a-5f00064f18e5@gmail.com> (raw)
In-Reply-To: <16abd8eb6a5c8398a030ae5d8919d5c8e92e2af1.1650376049.git.codeagain@codeagain.dev>
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?
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-04-20 6:07 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 [this message]
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
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=ed6cd79c-6a1d-8299-c90a-5f00064f18e5@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).