[Gluster-devel] patch #10954

Sakshi Bansal sabansal at redhat.com
Thu Jan 28 09:50:42 UTC 2016


Just checking if the changes made to brick_up_status by patch #12913 are required in 3.7 as well (since it is not backported)

----- Original Message -----
From: "Ravishankar N" <ravishankar at redhat.com>
To: "Venky Shankar" <vshankar at redhat.com>, "Sakshi Bansal" <sabansal at redhat.com>
Cc: "Ravishankar Narayanankutty" <ranaraya at redhat.com>, "Gluster Devel" <gluster-devel at gluster.org>
Sent: Thursday, January 28, 2016 2:21:18 PM
Subject: Re: [Gluster-devel] patch #10954

On 01/28/2016 12:50 PM, Venky Shankar wrote:
> Yes, that should be good. Better to have just one version of the routine. Also, I
> think Ravi found a bug in brick_up_status() [or the _1 version?].
http://review.gluster.org/12913 fixed it upstream already. It wasn't 
sent to 3.7.
I think the patch http://review.gluster.org/13276 in 3.7  probably 
hand-copied brick_up_status() from an earlier git HEAD


>   So, that should
> also be incorporated.
>
> You'll probably get a conflict during backport as the routine was hand copied.
>
>> >




More information about the Gluster-devel mailing list