CEPH filesystem development
 help / color / mirror / Atom feed
From: Guido Winkelmann <guido-ceph@thisisnotatest.de>
To: Alex Elsayed <eternaleye@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: RBD layering design draft
Date: Fri, 22 Jun 2012 16:41:55 +0200	[thread overview]
Message-ID: <13965457.S14qi4B5iq@pc10> (raw)
In-Reply-To: <loom.20120622T035754-492@post.gmane.org>

Am Freitag, 22. Juni 2012, 02:02:38 schrieb Alex Elsayed:
> Dan Mick <dan.mick <at> inktank.com> writes:
> > On 06/18/2012 11:01 AM, Sage Weil wrote:
> > > On Mon, 18 Jun 2012, Josh Durgin wrote:
> > >>>>      $ rbd copyup pool2/child1
> > 
> > "disown" and "adopt"?  :)  (actually I started as a joke, but really I
> > kinda like that; fits with the parent-child name)
> 
> The issue I see with that is that the argument refers to the child rather
> than the parent, so it doesn't match. I personally like 'unshare' since
> it'll also work in the dedup case, but if we stick with the parent/child
> terminology 'emancipate' might work (although it lacks a good reverse).

AFAIK the word started in ancient Rome as meaning to release slaves into 
freedom, so I suppose the opposite would be enslave?

	Guido

  reply	other threads:[~2012-06-22 14:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-15 20:48 RBD layering design draft Josh Durgin
2012-06-16  0:46 ` Sage Weil
2012-06-16  2:00   ` Yehuda Sadeh
2012-06-16 15:11     ` Sage Weil
2012-06-17 13:42       ` Martin Mailand
2012-06-18 18:04         ` Gregory Farnum
2012-06-18 16:25   ` Tommi Virtanen
2012-06-18 23:10     ` Dan Mick
2012-06-18 17:00 ` Tommi Virtanen
2012-06-18 17:14   ` Josh Durgin
2012-06-18 18:01     ` Sage Weil
2012-06-18 23:07       ` Dan Mick
2012-06-22  2:02         ` Alex Elsayed
2012-06-22 14:41           ` Guido Winkelmann [this message]
2012-06-22 14:36   ` Guido Winkelmann
2012-06-22 16:00     ` Tommi Virtanen
2012-06-21 21:51 ` Alex Elder
2012-06-22 14:37   ` Guido Winkelmann
2012-06-22 16:27   ` Tommi Virtanen

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=13965457.S14qi4B5iq@pc10 \
    --to=guido-ceph@thisisnotatest.de \
    --cc=ceph-devel@vger.kernel.org \
    --cc=eternaleye@gmail.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