Re: [Gluster-devel] reagarding backport information while porting patches

On 06/23/2017 10:19 AM, Shyam wrote: On 06/23/2017 10:11 AM, Pranith Kumar Karampuri wrote: On Fri, Jun 23, 2017 at 7:24 PM, Shyam > wrote: On 06/23/2017 09:48 AM, Pranith Kumar Karampuri wrote: On Fri, Jun 23, 2017 at 7:06 PM,

Re: [Gluster-devel] reagarding backport information while porting patches

On 06/23/2017 10:11 AM, Pranith Kumar Karampuri wrote: On Fri, Jun 23, 2017 at 7:24 PM, Shyam > wrote: On 06/23/2017 09:48 AM, Pranith Kumar Karampuri wrote: On Fri, Jun 23, 2017 at 7:06 PM, Shyam

Re: [Gluster-devel] reagarding backport information while porting patches

On Fri, Jun 23, 2017 at 7:24 PM, Shyam wrote: > On 06/23/2017 09:48 AM, Pranith Kumar Karampuri wrote: > >> >> >> On Fri, Jun 23, 2017 at 7:06 PM, Shyam > > wrote: >> >> On 06/23/2017 07:00 AM, Pranith Kumar Karampuri

Re: [Gluster-devel] reagarding backport information while porting patches

On 06/23/2017 09:48 AM, Pranith Kumar Karampuri wrote: On Fri, Jun 23, 2017 at 7:06 PM, Shyam > wrote: On 06/23/2017 07:00 AM, Pranith Kumar Karampuri wrote: Note that all of this is just my opinion, and based on

Re: [Gluster-devel] reagarding backport information while porting patches

On Fri, Jun 23, 2017 at 7:06 PM, Shyam wrote: > On 06/23/2017 07:00 AM, Pranith Kumar Karampuri wrote: > >> Note that all of this is just my opinion, and based on working with >> many >> different projects that use git (or other tools) to identify patches >> that

Re: [Gluster-devel] reagarding backport information while porting patches

On 06/23/2017 07:00 AM, Pranith Kumar Karampuri wrote: Note that all of this is just my opinion, and based on working with many different projects that use git (or other tools) to identify patches that could be candidates for backporting. In general, the more details that are

[Gluster-devel] Coverity covscan for 2017-06-23-d66fb14a (master branch)

GlusterFS Coverity covscan results are available from http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-06-23-d66fb14a ___ Gluster-devel mailing list Gluster-devel@gluster.org

Re: [Gluster-devel] Introducing minister

Adding gluster-devel On Fri, Jun 23, 2017 at 5:52 PM, Raghavendra Talur wrote: > Hi All, > > Kubernetes and Openshift have amazing projects called minikube and > minishift which make it very easy to setup those distributed systems > for easy development. As the Gluster

Re: [Gluster-devel] Regression Voting Changes

On Wed, Jun 21, 2017 at 7:19 PM, Nigel Babu wrote: > On Wed, Jun 21, 2017 at 06:05:32PM +0530, Atin Mukherjee wrote: > > On Tue, Jun 20, 2017 at 9:17 AM, Nigel Babu wrote: > > > > > Hello folks, > > > > > > Amar has proposed[1] these changes in the past and

Re: [Gluster-devel] reagarding backport information while porting patches

On Fri, Jun 23, 2017 at 4:21 PM, Niels de Vos wrote: > On Fri, Jun 23, 2017 at 03:53:42PM +0530, Pranith Kumar Karampuri wrote: > > On Fri, Jun 23, 2017 at 3:01 PM, Niels de Vos wrote: > > > > > On Fri, Jun 23, 2017 at 01:47:57PM +0530, Pranith Kumar

Re: [Gluster-devel] reagarding backport information while porting patches

On Fri, Jun 23, 2017 at 03:53:42PM +0530, Pranith Kumar Karampuri wrote: > On Fri, Jun 23, 2017 at 3:01 PM, Niels de Vos wrote: > > > On Fri, Jun 23, 2017 at 01:47:57PM +0530, Pranith Kumar Karampuri wrote: > > > On Fri, Jun 23, 2017 at 1:30 PM, Niels de Vos

Re: [Gluster-devel] [Gluster-Maintainers] Release 3.11.1: Scheduled for 20th of June

On 22 June 2017 at 22:44, Pranith Kumar Karampuri wrote: > > > On Wed, Jun 21, 2017 at 9:12 PM, Shyam wrote: > >> On 06/21/2017 11:37 AM, Pranith Kumar Karampuri wrote: >> >>> >>> >>> On Tue, Jun 20, 2017 at 7:37 PM, Shyam >>

Re: [Gluster-devel] ./tests/encryption/crypt.t fails regression with core

On Fri, Jun 23, 2017 at 10:44:21AM +0530, Amar Tumballi wrote: > On Thu, Jun 22, 2017 at 9:22 PM, Atin Mukherjee wrote: > > > I have highlighted about this failure earlier at [1] > > > > [1] http://lists.gluster.org/pipermail/gluster-devel/2017-June/053042.html > > > > > If

Re: [Gluster-devel] reagarding backport information while porting patches

On Fri, Jun 23, 2017 at 01:47:57PM +0530, Pranith Kumar Karampuri wrote: > On Fri, Jun 23, 2017 at 1:30 PM, Niels de Vos wrote: > > > On Fri, Jun 23, 2017 at 09:15:21AM +0530, Pranith Kumar Karampuri wrote: > > > hi, > > > Now that we are doing backports with same

Re: [Gluster-devel] reagarding backport information while porting patches

On Fri, Jun 23, 2017 at 1:30 PM, Niels de Vos wrote: > On Fri, Jun 23, 2017 at 09:15:21AM +0530, Pranith Kumar Karampuri wrote: > > hi, > > Now that we are doing backports with same Change-Id, we can find the > > patches and their backports both online and in the tree

Re: [Gluster-devel] reagarding backport information while porting patches

On Fri, Jun 23, 2017 at 09:15:21AM +0530, Pranith Kumar Karampuri wrote: > hi, > Now that we are doing backports with same Change-Id, we can find the > patches and their backports both online and in the tree without any extra > information in the commit message. So shall we stop adding text

Re: [Gluster-devel] reagarding backport information while porting patches

On Fri, Jun 23, 2017 at 9:37 AM, Ravishankar N wrote: > On 06/23/2017 09:15 AM, Pranith Kumar Karampuri wrote: > > hi, > Now that we are doing backports with same Change-Id, we can find the > patches and their backports both online and in the tree without any extra >