[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-block] [PATCH v3] block/gluster: Handle changed glfs_ftruncate

From: Eric Blake
Subject: Re: [Qemu-block] [PATCH v3] block/gluster: Handle changed glfs_ftruncate signature
Date: Wed, 1 Aug 2018 10:17:28 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0

On 08/01/2018 06:47 AM, Niels de Vos wrote:
If glusterfs-5 releases in October, that may line up with 3.1 or 3.2.

Ok, I'll keep these kind of patches in my tree as work-in-progress and
when the glusterfs-5 gets tagged for alpha/beta send it again.

Even if not optimal, would you accept this as a way going forward?

It will work. But even better would be getting gluster to the point that it has a stable back-compat API guarantee (no future API removals or signature changes on existing functions - all new functionality is added via new API). The more clients a library gains, the more pain you cause yourself and all your clients when you choose not to maintain a backwards-compatible stable API.

Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

reply via email to

[Prev in Thread] Current Thread [Next in Thread]