On Fri, Jul 18, 2014 at 11:15:37AM +0530, Vijay Bellur wrote:
On 07/18/2014 08:54 AM, Pranith Kumar Karampuri wrote:
On 07/18/2014 12:08 AM, Vijay Bellur wrote:
On 07/17/2014 01:43 AM, Niels de Vos wrote:
Meeting summary
---
*
On Fri, Jul 18, 2014 at 11:39 AM, Pranith Kumar Karampuri
pkara...@redhat.com wrote:
On 07/18/2014 11:22 AM, Kaushal M wrote:
On Fri, Jul 18, 2014 at 11:11 AM, Pranith Kumar Karampuri
pkara...@redhat.com wrote:
On 07/17/2014 07:25 PM, Kaushal M wrote:
I came across mediawiki's developer
Hi,
Created a bug against the same. Please use it to submit if required.
https://bugzilla.redhat.com/show_bug.cgi?id=1121014
Thanks
Varun Shastry
On Tuesday 15 July 2014 09:34 PM, Pranith Kumar Karampuri wrote:
On 07/15/2014 09:24 PM, Joseph Fernandes wrote:
Hi Pranith,
Could you please
[Adding gluster-devel]
On 07/18/2014 05:20 PM, Andrew Lau wrote:
Hi all,
As most of you have got hints from previous messages, hosted engine
won't work on gluster . A quote from BZ1097639
Using hosted engine with Gluster backed storage is currently something
we really warn against.
I think
On Fri, Jul 18, 2014 at 10:06 PM, Vijay Bellur vbel...@redhat.com wrote:
[Adding gluster-devel]
On 07/18/2014 05:20 PM, Andrew Lau wrote:
Hi all,
As most of you have got hints from previous messages, hosted engine
won't work on gluster . A quote from BZ1097639
Using hosted engine
On 2014-07-17 20:22, Vijay Bellur wrote:
Hi All,
A new branch, 'release-3.6', has been branched from this commit in
master:
commit 950f9d8abe714708ca62b86f304e7417127e1132 Author: Jeff Darcy
jda...@redhat.com Date: Tue Jul 8 21:56:04 2014 -0400
dht: fix rename race
You can
On 07/18/2014 07:57 PM, Anders Blomdell wrote:
During testing of a 3*4 gluster (from master as of yesterday), I encountered
two major weirdnesses:
1. A 'rm -rf some_dir' needed several invocations to finish, each time
reporting a number of lines like these:
rm: cannot remove
On 07/18/2014 07:57 PM, Anders Blomdell wrote:
During testing of a 3*4 gluster (from master as of yesterday), I encountered
two major weirdnesses:
1. A 'rm -rf some_dir' needed several invocations to finish, each time
reporting a number of lines like these:
rm: cannot remove
