[PATCH] community/ceph: move from main
Export this patch
---
{main => community}/ceph/APKBUILD | 0
{main => community}/ceph/allperms.patch | 0
{main => community}/ceph/boost-1.70.patch | 0
{main => community}/ceph/ceph-user.pre-install | 0
{main => community}/ceph/musl-fixes.patch | 0
5 files changed, 0 insertions(+), 0 deletions(-)
rename {main => community}/ceph/APKBUILD (100%)
rename {main => community}/ceph/allperms.patch (100%)
rename {main => community}/ceph/boost-1.70.patch (100%)
rename {main => community}/ceph/ceph-user.pre-install (100%)
rename {main => community}/ceph/musl-fixes.patch (100%)
diff --git a/main/ceph/APKBUILD b/community/ceph/APKBUILD
similarity index 100%
rename from main/ceph/APKBUILD
rename to community/ceph/APKBUILD
diff --git a/main/ceph/allperms.patch b/community/ceph/allperms.patch
similarity index 100%
rename from main/ceph/allperms.patch
rename to community/ceph/allperms.patch
diff --git a/main/ceph/boost-1.70.patch b/community/ceph/boost-1.70.patch
similarity index 100%
rename from main/ceph/boost-1.70.patch
rename to community/ceph/boost-1.70.patch
diff --git a/main/ceph/ceph-user.pre-install b/community/ceph/ceph-user.pre-install
similarity index 100%
rename from main/ceph/ceph-user.pre-install
rename to community/ceph/ceph-user.pre-install
diff --git a/main/ceph/musl-fixes.patch b/community/ceph/musl-fixes.patch
similarity index 100%
rename from main/ceph/musl-fixes.patch
rename to community/ceph/musl-fixes.patch
--
2.24.0
Hi Drew,
Why should we revert 286830029a1b2 (main/ceph: Move ceph from
community) and move it back to community? Your commit message does not
explain why we move it back after 2 months.
The commit message for commit 286830029a1b2 says:
> This move should allow us to enable ceph support in Qemu
Does this mean that you don't want qemu with ceph support or do you
think we should move qemu to community too?
Thanks!
-nc
On Mon, 9 Dec 2019 13:36:35 -0500
Drew DeVault <sir@cmpwn.com> wrote: