From: Chris Mason <chris.mason@fusionio.com>
To: David Sterba <dsterba@suse.cz>, <linux-btrfs@vger.kernel.org>
Cc: David Sterba <dsterba@suse.cz>, <linux-doc@vger.kernel.org>
Subject: Re: [PATCH 1/2 v2] Documentation: filesystems: add new btrfs mount options
Date: Thu, 21 Nov 2013 11:53:06 -0500 [thread overview]
Message-ID: <20131121165306.5312.230@localhost.localdomain> (raw)
In-Reply-To: <1385052483-30220-1-git-send-email-dsterba@suse.cz>
Quoting David Sterba (2013-11-21 11:48:03)
> Two new options were added in 3.12: commit and rescan_uuid_tree
>
> CC: linux-doc@vger.kernel.org
> Signed-off-by: David Sterba <dsterba@suse.cz>
> ---
> v2: fix typo pointed out by Stefan
You just caught me before the pull request. V1 was already in
for-linus, so I rebased this one in.
-chris
prev parent reply other threads:[~2013-11-21 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 14:05 [PATCH 1/2] Documentation: filesystems: add new btrfs mount options David Sterba
2013-11-21 8:44 ` Stefan Behrens
2013-11-21 16:48 ` [PATCH 1/2 v2] " David Sterba
2013-11-21 16:53 ` Chris Mason [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=20131121165306.5312.230@localhost.localdomain \
--to=chris.mason@fusionio.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-doc@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).