Adding in Eric and Steve.
Ric
On Oct 18, 2017 9:35 AM, "Raghavendra G" wrote:
+Brian Foster
On Wed, Oct 11, 2017 at 4:11 PM, Raghavendra G
wrote:
> We ran into a regression [2][3]. Hence reviving this thread.
>
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1500269
> [3] https://review.g
+Brian Foster
On Wed, Oct 11, 2017 at 4:11 PM, Raghavendra G
wrote:
> We ran into a regression [2][3]. Hence reviving this thread.
>
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1500269
> [3] https://review.gluster.org/18463
>
> On Thu, Mar 31, 2016 at 1:22 AM, J. Bruce Fields
> wrote:
>
>
GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-10-17-4f3c680e
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman
On Thu, Oct 12, 2017 at 10:28:01AM +0530, Nithya Balachandran wrote:
> On 12 October 2017 at 10:12, Raghavendra Talur wrote:
>
> > On Wed, Oct 11, 2017 at 8:35 PM, Shyam Ranganathan
> > wrote:
> > > Hi,
> > >
> > > Recently I was in some conversations that mentioned having to hunt for
> > the
>
On Thu, Oct 12, 2017 at 6:09 PM, Shyam Ranganathan wrote:
> On 10/12/2017 12:58 AM, Nithya Balachandran wrote:
>>
>> > - When to mark the blocker bug as dependent on another bug:
>> >
>> > Blockers are meant to track *just* blockers for a major or minor
>> release,
>> > not
