From: Anand Jain <anand.jain@oracle.com>
To: Hans van Kranenburg <hans@knorrie.org>, linux-btrfs@vger.kernel.org
Cc: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
Subject: Re: [PATCH] btrfs-progs: docs: fix label property description
Date: Tue, 6 Aug 2019 23:20:27 +0800 [thread overview]
Message-ID: <f2b90bc0-1a23-5879-d3d4-e0c1b259e1cc@oracle.com> (raw)
In-Reply-To: <20190803214403.1040-1-hans@knorrie.org>
On 8/4/19 5:44 AM, Hans van Kranenburg wrote:
> From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
>
> Recently, commit c9da5695b2 improved the description for the label
> property, to clarify it's a filesystem property, and not a device
> property. Follow this change in the man page for btrfs-property.
>
> Also add a little hint about what to specify as object.
>
> Signed-off-by: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
Reviewed-by: Anand Jain <anand.jain@oracle.com>
> ---
> Documentation/btrfs-property.asciidoc | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/btrfs-property.asciidoc b/Documentation/btrfs-property.asciidoc
> index b562717b..47960833 100644
> --- a/Documentation/btrfs-property.asciidoc
> +++ b/Documentation/btrfs-property.asciidoc
> @@ -43,7 +43,8 @@ the following:
> ro::::
> read-only flag of subvolume: true or false
> label::::
> -label of device
> +label of the filesystem. For an unmounted filesystem, provide a path to a block
> +device as object. For a mounted filesystem, specify a mount point.
> compression::::
> compression algorithm set for an inode, possible values: 'lzo', 'zlib', 'zstd'.
> To disable compression use "" (empty string), 'no' or 'none'.
>
next prev parent reply other threads:[~2019-08-06 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-03 21:44 [PATCH] btrfs-progs: docs: fix label property description Hans van Kranenburg
2019-08-06 15:20 ` Anand Jain [this message]
2019-08-06 16:49 ` David Sterba
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=f2b90bc0-1a23-5879-d3d4-e0c1b259e1cc@oracle.com \
--to=anand.jain@oracle.com \
--cc=hans.van.kranenburg@mendix.com \
--cc=hans@knorrie.org \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).