On Fri, Nov 10, 2017 at 10:40 AM, Niels de Vos wrote:
> On Thu, Nov 09, 2017 at 06:01:10PM -0500, Jeff Darcy wrote:
>> > So - nothing inherent to libfuse and nothing that would be relevant as
>> > of today.
>> >
>> > But then, let me put it like this: what reason could we have to *not* go
>> > wit
On Fri, Nov 10, 2017 at 12:01 AM, Jeff Darcy wrote:
>> So - nothing inherent to libfuse and nothing that would be relevant as
>> of today.
>>
>> But then, let me put it like this: what reason could we have to *not* go
>> with xglfs in 4.0? It's true that the deliverables are present in libfuse
>>
On Thu, Nov 09, 2017 at 06:01:10PM -0500, Jeff Darcy wrote:
> > So - nothing inherent to libfuse and nothing that would be relevant as
> > of today.
> >
> > But then, let me put it like this: what reason could we have to *not* go
> > with xglfs in 4.0? It's true that the deliverables are present i
> So - nothing inherent to libfuse and nothing that would be relevant as
> of today.
>
> But then, let me put it like this: what reason could we have to *not* go
> with xglfs in 4.0? It's true that the deliverables are present in libfuse
> and
> libgfapi and it's just a thin glue. As such it seems
On Thu, Nov 9, 2017 at 1:33 PM, Niels de Vos wrote:
>
> On Thu, Nov 09, 2017 at 01:04:48AM +0100, Csaba Henk wrote:
> > Hello list,
> >
> > here is an overview of recent additions to the
> > FUSE protocol that are not yet supported by
> > the GlusterFS FUSE implementation and
> > what sh/could be
On Thu, Nov 09, 2017 at 01:04:48AM +0100, Csaba Henk wrote:
> Hello list,
>
> here is an overview of recent additions to the
> FUSE protocol that are not yet supported by
> the GlusterFS FUSE implementation and
> what sh/could be done about them.
>
> https://docs.google.com/document/d/1VGxMC7Db7R
Hello list,
here is an overview of recent additions to the
FUSE protocol that are not yet supported by
the GlusterFS FUSE implementation and
what sh/could be done about them.
https://docs.google.com/document/d/1VGxMC7Db7Rdd19VXlBe0tI-frdjICJdzxx4EsntuPDU/edit
Comments on the doc or in this threa
