From: Shuah Khan <skhan@linuxfoundation.org>
To: Nihar Chaithanya <niharchaithanya@gmail.com>, corbet@lwn.net
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] docs:process:changes: fix version command for btrfs-progs
Date: Mon, 14 Oct 2024 17:09:51 -0600 [thread overview]
Message-ID: <9e75fba9-08aa-439c-9c26-a4f50a9a8372@linuxfoundation.org> (raw)
In-Reply-To: <20241012141425.11852-1-niharchaithanya@gmail.com>
On 10/12/24 08:14, Nihar Chaithanya wrote:
> The command given in the changes.rst document to check the version of
> btrfs-progs is:
> -> btrfsck
Just use spaces - remove ->
> which does not output the version, and according to manual page of the
> btrfs-progs the command to check the version of btrfs-progs is:
> -> btrfs --version
Same here
You can simply the change log to say the following:
btrfs is the right command to check btrfs-progs version.
Change the command to check btrfs-progs version in the
changes.rst document
>
> Add a fix changing the command to check the version of btrfs-progs.
>
> Signed-off-by: Nihar Chaithanya <niharchaithanya@gmail.com>
> ---
> Documentation/process/changes.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/process/changes.rst b/Documentation/process/changes.rst
> index 00f1ed7c59c3..82b5e378eebf 100644
> --- a/Documentation/process/changes.rst
> +++ b/Documentation/process/changes.rst
> @@ -46,7 +46,7 @@ jfsutils 1.1.3 fsck.jfs -V
> reiserfsprogs 3.6.3 reiserfsck -V
> xfsprogs 2.6.0 xfs_db -V
> squashfs-tools 4.0 mksquashfs -version
> -btrfs-progs 0.18 btrfsck
> +btrfs-progs 0.18 btrfs --version
> pcmciautils 004 pccardctl -V
> quota-tools 3.09 quota -V
> PPP 2.4.0 pppd --version
thanks,
-- Shuah
prev parent reply other threads:[~2024-10-14 23:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 14:14 Nihar Chaithanya
2024-10-14 23:09 ` Shuah Khan [this message]
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=9e75fba9-08aa-439c-9c26-a4f50a9a8372@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=niharchaithanya@gmail.com \
--cc=workflows@vger.kernel.org \
/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