[ This retries commit d4b13963f217 which was reverted in 766741fcaa1f.
In this version we require only `sizeof(fuse_in_header) +
sizeof(fuse_write_in)`
instead of 4K for FUSE request header room, because, contrary to
libfuse and kernel client behaviour, GlusterFS actually provides only
so
I have sent a rfc patch [1] for review.
https://review.gluster.org/#/c/glusterfs/+/23011/
On Thu, Jul 4, 2019 at 1:13 AM Pranith Kumar Karampuri
wrote:
>
>
> On Wed, Jul 3, 2019 at 10:59 PM FNU Raghavendra Manjunath <
> rab...@redhat.com> wrote:
>
>>
>>
>> On Wed, Jul 3, 2019 at 3:28 AM Pranith
I'll make the changes for prioritizing python2 over 3 for release 5 and 4.
Let me know if we need to make any other changes.
Thanks!
On Mon, Jul 8, 2019 at 3:07 PM Niels de Vos wrote:
>
> On Mon, Jul 08, 2019 at 02:37:34PM +0530, Hari Gowtham wrote:
> > I have a few concerns about adding the pyt
On Mon, Jul 08, 2019 at 02:37:34PM +0530, Hari Gowtham wrote:
> I have a few concerns about adding the python3 devel package and
> continuing the build.
> In the effort to make Gluster python3 compatible,
> https://github.com/gluster/glusterfs/issues/411
> I think we have decided to skip working on
I have a few concerns about adding the python3 devel package and
continuing the build.
In the effort to make Gluster python3 compatible,
https://github.com/gluster/glusterfs/issues/411
I think we have decided to skip working on Glupy to make it python3 compatible.
(Correct me if i'm wrong.) As Glup
