From: Chris Mason <chris.mason@oracle.com>
To: Jian Lin <lj@linjian.org>
Cc: "Pádraig Brady" <P@draigbrady.com>,
bug-coreutils@gnu.org, linux-btrfs@vger.kernel.org
Subject: Re: A file cloned with "cp --reflink" different from the original one?
Date: Mon, 23 Nov 2009 10:52:13 -0500 [thread overview]
Message-ID: <20091123155213.GE15294@think> (raw)
In-Reply-To: <119341710911230750j10502561xac71cfd37ad9a649@mail.gmail.com>
On Mon, Nov 23, 2009 at 11:50:47PM +0800, Jian Lin wrote:
> Thanks. I will try the new version soon.
Note that you'll have to reclone the files, the new version won't fix
the old clone I'm afraid.
-chris
prev parent reply other threads:[~2009-11-23 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <119341710911230208j5e60734cvf09cfcacd86ba9f6@mail.gmail.com>
[not found] ` <4B0A8FC1.4050208@draigBrady.com>
[not found] ` <119341710911230614h10d7071dq3700cdf39e0c28fb@mail.gmail.com>
2009-11-23 15:47 ` A file cloned with "cp --reflink" different from the original one? Pádraig Brady
2009-11-23 15:50 ` Jian Lin
2009-11-23 15:52 ` 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=20091123155213.GE15294@think \
--to=chris.mason@oracle.com \
--cc=P@draigbrady.com \
--cc=bug-coreutils@gnu.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=lj@linjian.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