From: Dan Mick <dan.mick@inktank.com>
To: Sage Weil <sage@inktank.com>
Cc: Danny Al-Gaaf <danny.al-gaaf@bisect.de>,
Gregory Farnum <greg@inktank.com>,
ceph-devel@vger.kernel.org,
Watkins Noah <noah.watkins@inktank.com>
Subject: Re: [PATCH 0/6] fix build (ceph.spec)
Date: Wed, 30 Jan 2013 21:10:45 -0800 [thread overview]
Message-ID: <5109FCD5.4040303@inktank.com> (raw)
In-Reply-To: <5109FC4C.1070407@inktank.com>
On 01/30/2013 09:08 PM, Dan Mick wrote:
>
>
> On 01/30/2013 11:55 AM, Sage Weil wrote:
>
>> I think the end goal is to build an rbd-fuse package, just like
>> ceph-fuse.
>> I'm not sure it matters how mature the tool is before it goes into the
>> package; as long as it is separate, people can not install it, and the
>> distros can keep it out of their supported repos as they like.
>
> I like that plan a lot better.
and the major reason it wasn't yet done is that there are no manpages,
tests, etc., but I wanted this to be available to experimenters.
next prev parent reply other threads:[~2013-01-31 5:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 18:00 [PATCH 0/6] fix build (ceph.spec) Danny Al-Gaaf
2013-01-30 18:00 ` [PATCH 1/6] Revert "Don't install rbd-fuse binary" Danny Al-Gaaf
2013-01-30 18:00 ` [PATCH 2/6] ceph.spec.in: add rbd-fuse Danny Al-Gaaf
2013-01-30 18:00 ` [PATCH 3/6] ceph.spec.in: move libcephfs_jni.so to ceph-devel Danny Al-Gaaf
2013-01-30 18:00 ` [PATCH 4/6] ceph.spec.in: don't move libcephfs_jni files around Danny Al-Gaaf
2013-01-30 18:00 ` [PATCH 5/6] ceph.spec.in: extend fix for libedit-devel on special SUSE versions Danny Al-Gaaf
2013-01-30 18:00 ` [PATCH 6/6] ceph.spec.in: fix file section for ceph-resource-agents Danny Al-Gaaf
2013-01-30 18:07 ` [PATCH 0/6] fix build (ceph.spec) Gregory Farnum
2013-01-30 18:30 ` Danny Al-Gaaf
2013-01-30 19:55 ` Sage Weil
2013-01-31 5:08 ` Dan Mick
2013-01-31 5:10 ` Dan Mick [this message]
2013-01-31 7:22 ` Gary Lowell
2013-02-01 7:00 ` Gary Lowell
2013-02-01 14:22 ` Danny Al-Gaaf
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=5109FCD5.4040303@inktank.com \
--to=dan.mick@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=danny.al-gaaf@bisect.de \
--cc=greg@inktank.com \
--cc=noah.watkins@inktank.com \
--cc=sage@inktank.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.