On 04/04/2017, J. Eric Ivancich wrote:
> An argument for making it a submodule is that ceph already uses submodules and ceph developers are familiar with working with (and around) them.
I think this would be the overriding argument. If both submodules and
subtrees have their own set of drawbacks, it seems like a bad idea for
Ceph as a project to have to deal with /both/ sets of drawbacks
instead of just one.
--
Senior Software Engineer Red Hat Storage, Ann Arbor, MI, US
IRC: Aemerson@{RedHat, OFTC}
0x80F7544B90EDBFB9 E707 86BA 0C1B 62CC 152C 7C12 80F7 544B 90ED BFB9
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
