On 03/05/2015 06:33 PM, Vijay Bellur wrote:
On 03/01/2015 11:44 PM, Atin Mukherjee wrote:
Thanks Fanghuang for your nice words.
Vijay,
Can we try to take this patch in for 3.7 ?
Happy to get this in to 3.7. Could you please rebase this patch to the
latest git HEAD?
I've rebased it.
On 03/01/2015 11:44 PM, Atin Mukherjee wrote:
Thanks Fanghuang for your nice words.
Vijay,
Can we try to take this patch in for 3.7 ?
Happy to get this in to 3.7. Could you please rebase this patch to the
latest git HEAD?
Thanks,
Vijay
~Atin
On 03/02/2015 08:01 AM,
Thanks Fanghuang for your nice words.
Vijay,
Can we try to take this patch in for 3.7 ?
~Atin
On 03/02/2015 08:01 AM, fanghuang.d...@yahoo.com wrote:
Hi Atin,
Thank you for your work on it. What is blocking the patch? Could you ping it
for the reviewers? Best Regards,
Fang Huang
Hi Atin,
Thank you for your work on it. What is blocking the patch? Could you ping it
for the reviewers? Best Regards,
Fang Huang
On Monday, 16 February 2015, 12:28, Atin Mukherjee amukh...@redhat.com
wrote:
On 02/13/2015 02:05 PM, Feng Wang wrote:
Hi all,
If we set the
On 02/13/2015 02:05 PM, Feng Wang wrote:
Hi all,
If we set the read-only feature using the following command in the cli to a
volume in service, it will not work until the volume is restarted.
That's the correct functionality. http://review.gluster.org/#/c/8571/
should address it, however it
Hi all,
If we set the read-only feature using the following command in the cli to a
volume in service, it will not work until the volume is restarted.
gluster volume set vol-name features.readonly on
It means that the service must be stopped temporarily. Does this make sense?
An alternative
