From: "Matt W. Benjamin" <matt@cohortfs.com>
To: ceph-devel <ceph-devel@vger.kernel.org>
Cc: Sage Weil <sage@newdream.net>
Subject: wip-claim-2
Date: Mon, 8 Dec 2014 16:48:16 -0500 (EST) [thread overview]
Message-ID: <1732608241.235.1418075296547.JavaMail.root@thunderbeast.private.linuxbox.com> (raw)
In-Reply-To: <1582070360.233.1418075135946.JavaMail.root@thunderbeast.private.linuxbox.com>
Hi devs,
We've created a new branch wip-claim-2, and new pull request https://github.com/linuxbox2/linuxbox-ceph/pull/3
based on review feedback.
The big change is to replace "volatile" with "sharable", and replace "strong_claim()" with "clone_nonsharable()."
This may not be perfect, feedback appreciated. It does remove the overloading of "claim()", which people found
confusing.
Thanks!
Matt
--
Matt Benjamin
CohortFS, LLC.
315 West Huron Street, Suite 140A
Ann Arbor, Michigan 48103
http://cohortfs.com
tel. 734-761-4689
fax. 734-769-8938
cel. 734-216-5309
next parent reply other threads:[~2014-12-08 21:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1582070360.233.1418075135946.JavaMail.root@thunderbeast.private.linuxbox.com>
2014-12-08 21:48 ` Matt W. Benjamin [this message]
2014-12-08 21:59 ` wip-claim-2 Sage Weil
2014-12-09 16:49 ` wip-claim-3: wip-claim-2 Matt W. Benjamin
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=1732608241.235.1418075296547.JavaMail.root@thunderbeast.private.linuxbox.com \
--to=matt@cohortfs.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@newdream.net \
/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