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

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] 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 >

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

On Fri, Jun 23, 2017 at 9:55 AM, Pranith Kumar Karampuri < pkara...@redhat.com> wrote: > > > 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

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 >

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

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 information in the commit message. So shall we stop adding text similar to: >

[Gluster-devel] reagarding backport information while porting patches

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 similar to: > Reviewed-on: https://review.gluster.org/17414 > Smoke: