So is there any one working on it to fix this issue either by this patch or some other way? if yes then please provide the time plan.
On Wed, May 31, 2017 at 4:25 PM, Amar Tumballi <atumb...@redhat.com> wrote: > > > On Wed, May 31, 2017 at 4:08 PM, ABHISHEK PALIWAL <abhishpali...@gmail.com > > wrote: > >> We are using 3.7.6 and on link https://review.gluster.org/#/c/16279 >> status is "can't merge" >> >> On Wed, May 31, 2017 at 4:05 PM, Amar Tumballi <atumb...@redhat.com> >> wrote: >> >>> This is already part of 3.11.0 release? >>> >> > Sorry about confusion! I was thinking of another patch. This patch is not > part of any releases yet. > > It says can't merge because it is failing regression tests and also looks > like it needs a rebase to latest master branch too. > > -Amar > > >>> On Wed, May 31, 2017 at 3:47 PM, ABHISHEK PALIWAL < >>> abhishpali...@gmail.com> wrote: >>> >>>> Hi Atin, >>>> >>>> Could you please let us know any time plan for deliver of this patch. >>>> >>>> Regards, >>>> Abhishek >>>> >>>> On Tue, May 9, 2017 at 6:37 PM, ABHISHEK PALIWAL < >>>> abhishpali...@gmail.com> wrote: >>>> >>>>> Actually it is very risky if it will reproduce in production thats is >>>>> why I said it is on high priority as want to resolve it before production. >>>>> >>>>> -- Regards Abhishek Paliwal
_______________________________________________ Gluster-users mailing list Gluster-users@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users
