public inbox for linux-unionfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Vivek Goyal <vgoyal@redhat.com>,
	overlayfs <linux-unionfs@vger.kernel.org>,
	Miklos Szeredi <miklos@szeredi.hu>,
	David Howells <dhowells@redhat.com>,
	fstests <fstests@vger.kernel.org>,
	Chandan Rajendra <chandan@linux.vnet.ibm.com>
Subject: Re: [ANNOUNCE] unionmount-testsuite: Amir's master branch updated
Date: Tue, 12 Dec 2017 11:10:21 +1100	[thread overview]
Message-ID: <20171212001021.GR4094@dastard> (raw)
In-Reply-To: <CAOQ4uxhb4yVTt29E0XFYY_OT_ubQ5w0Zgqojn=y7nH+XSZ90GA@mail.gmail.com>

On Mon, Dec 11, 2017 at 10:47:15PM +0200, Amir Goldstein wrote:
> On Mon, Dec 11, 2017 at 9:59 PM, Vivek Goyal <vgoyal@redhat.com> wrote:
> > - For the xfs reflink test, I am curious that why have you recommended
> >   to also enabled "rmapbt=1". Is is required for the tests?
> >
> 
> You cannot enable reflink=1 without it.

Yes you can. They are two different functions, used for completely
different things. They both landed at the same time, will end up
being fully supported at the same time, and probably get turned on
by default at the same time. But they are independent options...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  parent reply	other threads:[~2017-12-12  0:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05 20:20 [ANNOUNCE] unionmount-testsuite: Amir's master branch updated Amir Goldstein
2017-12-06  9:09 ` Miklos Szeredi
2017-12-06 18:17 ` Vivek Goyal
2017-12-06 19:14   ` Amir Goldstein
2017-12-08 16:29     ` Amir Goldstein
2017-12-11 19:59       ` Vivek Goyal
2017-12-11 20:47         ` Amir Goldstein
2017-12-11 20:59           ` Vivek Goyal
2017-12-12  0:10           ` Dave Chinner [this message]
2017-12-12  6:02             ` Amir Goldstein
2017-12-12 14:53             ` Christoph Hellwig
2017-12-12 15:00               ` Amir Goldstein

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=20171212001021.GR4094@dastard \
    --to=david@fromorbit.com \
    --cc=amir73il@gmail.com \
    --cc=chandan@linux.vnet.ibm.com \
    --cc=dhowells@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=vgoyal@redhat.com \
    /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