From: Gionatan Danti <g.danti@assyoma.it>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org, Gionatan Danti <g.danti@assyoma.it>
Subject: Re: XFS and reflink status
Date: Tue, 31 Oct 2017 10:36:28 +0100 [thread overview]
Message-ID: <2e64d152-dffc-08a9-7fd8-4c61ec1d050e@assyoma.it> (raw)
In-Reply-To: <20171030184045.GC4911@magnolia>
On 30/10/2017 19:40, Darrick J. Wong wrote:
> On Mon, Oct 30, 2017 at 07:18:50PM +0100, Gionatan Danti wrote:
>> Il 22-10-2017 21:13 Gionatan Danti ha scritto:
>>> Hi all,
>>> I would like to know the current XFS reflink status, especially if it
>>> still an experimental feature or not.
>>>
>>> In one of the latest discussion I found [1], reflink is still marked
>>> as experimental/not stable. Any changes on that?
>
> No.
>
>>> If not, do you have
>>> any ETA on declaring it stable?
>
> When it's ready.
>
> --D
>
Fair enough ;)
Thanks for reporting.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
prev parent reply other threads:[~2017-10-31 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-22 19:13 XFS and reflink status Gionatan Danti
2017-10-30 18:18 ` Gionatan Danti
2017-10-30 18:40 ` Darrick J. Wong
2017-10-31 9:36 ` Gionatan Danti [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=2e64d152-dffc-08a9-7fd8-4c61ec1d050e@assyoma.it \
--to=g.danti@assyoma.it \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@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).