All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <jlbec@evilplan.org>
To: Richard Laager <rlaager@wiktel.com>
Cc: Joel Becker <Joel.Becker@oracle.com>, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] The reflink(2) system call v5.
Date: Tue, 7 Feb 2012 08:58:43 -0800	[thread overview]
Message-ID: <20120207165843.GB16994@dhcp-172-17-9-228.mtv.corp.google.com> (raw)
In-Reply-To: <1328420015.5007.303.camel@watermelon.coderich.net>

On Sat, Feb 04, 2012 at 11:38:31PM -0600, Richard Laager wrote:
> On Mon, 2009-09-14 at 22:24 -0500, Joel Becker wrote:
> > Here's v5 of reflink().
> 
> So, what ever happened with reflink(2)? This [0] is the last message I
> can find on the topic and it doesn't seem to have been merged.

	It's gone through two name changes (-> copyfile -> fastcopy) and
I owe an updated patch.

Joel

> 
> [0] http://marc.info/?l=linux-fsdevel&m=125296717319013&w=2
> 
> -- 
> Richard



-- 

"Get right to the heart of matters.
 It's the heart that matters more."

			http://www.jlbec.org/
			jlbec@evilplan.org

  reply	other threads:[~2012-02-07 16:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1328419914.5007.301.camel@watermelon.coderich.net>
2012-02-05  5:33 ` [RFC] The reflink(2) system call v5 Richard Laager
2012-02-07 16:58   ` Joel Becker [this message]
2009-05-03  6:15 [RFC] The reflink(2) system call Joel Becker
2009-05-07 22:15 ` [RFC] The reflink(2) system call v2 Joel Becker
2009-05-08  2:59   ` jim owens
2009-05-08  3:10     ` Joel Becker
2009-05-11 20:40       ` [RFC] The reflink(2) system call v4 Joel Becker
2009-05-28  0:24         ` [RFC] The reflink(2) system call v5 Joel Becker
2009-09-14 22:24         ` Joel Becker
2009-09-14 22:24         ` Joel Becker

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=20120207165843.GB16994@dhcp-172-17-9-228.mtv.corp.google.com \
    --to=jlbec@evilplan.org \
    --cc=Joel.Becker@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=rlaager@wiktel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.