[Gluster-Maintainers] Don't merge changes on release-3.7
Kaushal M
kshlmster at gmail.com
Sat Apr 16 02:02:25 UTC 2016
I've merged this change as it had passed all the jobs, and doesn't
seem (to me) to have any unexpected side effects.
On Sat, Apr 16, 2016 at 7:24 AM, Kaushal M <kshlmster at gmail.com> wrote:
> As I understand it's just a regression in the log messages. Does it
> have any impact on functionality?
>
> On Fri, Apr 15, 2016 at 6:42 PM, Vijaikumar Mallikarjuna
> <vmallika at redhat.com> wrote:
>> There is a regression bug:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1325822 with recent fix.
>>
>> This regression bug has been fixed in master, can we take this patch for
>> 3.7.11?
>>
>> Here is the 3.7 patch: http://review.gluster.org/#/c/13962/
>>
>> Thanks,
>> Vijay
>>
>>
>> On Thu, Apr 7, 2016 at 10:14 AM, Kaushal M <kshlmster at gmail.com> wrote:
>>>
>>> Hi All,
>>>
>>> I'm tagging 3.7.11, so please don't merge anymore changes on the
>>> release-3.7 branch.
>>>
>>> I'm currently on commit 458d4ba, which will be tagged as v3.7.11.
>>>
>>> I'll notify once the tagging is done, and merging changes can be resumed.
>>>
>>> Thanks,
>>> Kaushal
>>> _______________________________________________
>>> maintainers mailing list
>>> maintainers at gluster.org
>>> http://www.gluster.org/mailman/listinfo/maintainers
>>
>>
More information about the maintainers
mailing list