ocfs2-devel.oss.oracle.com archive mirror
 help / color / mirror / Atom feed
From: Gang He <ghe@suse.com>
To: Herbert Van Den Bergh <herbert.van.den.bergh@oracle.com>
Cc: "ocfs2-tools@oss.oracle.com" <ocfs2-tools@oss.oracle.com>,
	"ocfs2-devel@oss.oracle.com" <ocfs2-devel@oss.oracle.com>
Subject: Re: [Ocfs2-devel] About the status of reflink-tools
Date: Fri, 29 Jan 2021 15:46:26 +0800	[thread overview]
Message-ID: <ce23a917-0cb1-065a-59b1-3e4789fb0d79@suse.com> (raw)
In-Reply-To: <3E55B25E-76CC-4FFE-BF98-0637BCB4D9CC@ORACLE.COM>

Hi Herbert,

On 2021/1/29 15:33, Herbert Van Den Bergh wrote:
> Hi Gang,
> The reflink functionality has been merged into the coreutils package/project. The cp command now has a —reflink option. Check it out. If this isn’t what you’re looking for, then please elaborate.
For the other tools, e.g. shared-du, shared-filefrag, where do you 
download the related source code? still coreutils? that means this part 
code is included/maintained by coreutils project?


> Thanks,
> Herbert.
>> On Jan 28, 2021, at 6:59 PM, Gang He <GHe@suse.com> wrote:
>> Hi Guys,
>> You know, ocfs2 reflink related utilities were maintained by a seperated project reflink-tools,
>> What is this project's status? e.g. who is maintaining it, where can we download the latest source code?
>> Thanks
>> Gang
>> _______________________________________________
>> Ocfs2-devel mailing list
>> Ocfs2-devel@oss.oracle.com
>> https://oss.oracle.com/mailman/listinfo/ocfs2-devel

Ocfs2-devel mailing list

  reply	other threads:[~2021-01-29  7:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29  2:59 [Ocfs2-devel] About the status of reflink-tools Gang He
2021-01-29  7:33 ` Herbert Van Den Bergh
2021-01-29  7:46   ` Gang He [this message]
2021-01-29 18:34     ` Wengang Wang
2021-02-01  3:42       ` Gang He
2021-02-01 17:20         ` Wengang Wang

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ce23a917-0cb1-065a-59b1-3e4789fb0d79@suse.com \
    --to=ghe@suse.com \
    --cc=herbert.van.den.bergh@oracle.com \
    --cc=ocfs2-devel@oss.oracle.com \
    --cc=ocfs2-tools@oss.oracle.com \


* 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).