On Jul 14, 2015, at 3:41 AM, Owen Synge osy...@suse.com wrote:
Dear Travis,
We clearly disagree in this area.
I hope me explaining my perspective is not seen as unhelpful.
On 07/09/2015 07:00 PM, Travis Rhoden wrote:
(2B) inflexible / complex include paths for shared code between
Hey Owen,
I haven't followed any of the conversations you've had in ceph-deploy
land, but I've been trying to keep track of the ones on ceph-devel et
al. I can't comment on very much of it because I suck at Python — I
can write C in any language, and do so! ;)
I interject this comment because
Dear Travis,
We clearly disagree in this area.
I hope me explaining my perspective is not seen as unhelpful.
On 07/09/2015 07:00 PM, Travis Rhoden wrote:
(2B) inflexible / complex include paths for shared code between facade
implementations.
I disagree here. There are plenty of places
Hi Gregory,
On 07/14/2015 01:03 PM, Gregory Farnum wrote:
Hey Owen,
I haven't followed any of the conversations you've had in ceph-deploy
land, but I've been trying to keep track of the ones on ceph-devel et
al. I can't comment on very much of it because I suck at Python — I
can write C in
