On 2016-01-08 at 12:03 +0530, Raghavendra Talur wrote:
> Top posting, this is a very old thread.
>
> Keeping in view the recent NetBSD problems and the number of bugs creeping
> in, I suggest we do these things right now:
>
> a. Change the gerrit merge type to fast forward only.
> As explained
On Jan 12, 2016 2:50 AM, "Niels de Vos" wrote:
>
> On Fri, Jan 08, 2016 at 12:46:09PM +0530, Raghavendra Talur wrote:
> > On Fri, Jan 8, 2016 at 12:28 PM, Kaushal M wrote:
> >
> > > On Fri, Jan 8, 2016 at 12:10 PM, Kaushal M
wrote:
>
Niels de Vos wrote:
> How would we handle patches that get sent by maintainers? Most
> developers that do code reviews will only +1 those changes. Those will
> never get automatically regression tested then. I dont think a
> maintainer should +2 their own patch immediately
On Jan 12, 2016 3:44 AM, "Michael Adam" wrote:
>
> On 2016-01-08 at 12:03 +0530, Raghavendra Talur wrote:
> > Top posting, this is a very old thread.
> >
> > Keeping in view the recent NetBSD problems and the number of bugs
creeping
> > in, I suggest we do these things right now:
- Original Message -
> From: "Raghavendra Talur" <rta...@redhat.com>
> To: "Michael Adam" <ob...@samba.org>
> Cc: "Gluster Devel" <gluster-devel@gluster.org>
> Sent: Tuesday, January 12, 2016 8:46:05 AM
> Subject: Re:
On Fri, Jan 08, 2016 at 12:46:09PM +0530, Raghavendra Talur wrote:
> On Fri, Jan 8, 2016 at 12:28 PM, Kaushal M wrote:
>
> > On Fri, Jan 8, 2016 at 12:10 PM, Kaushal M wrote:
> > > On Fri, Jan 8, 2016 at 12:03 PM, Raghavendra Talur
>
Top posting, this is a very old thread.
Keeping in view the recent NetBSD problems and the number of bugs creeping
in, I suggest we do these things right now:
a. Change the gerrit merge type to fast forward only.
As explained below in the thread, with our current setup even if both
PatchA and
On Fri, Jan 8, 2016 at 12:10 PM, Kaushal M wrote:
> On Fri, Jan 8, 2016 at 12:03 PM, Raghavendra Talur wrote:
>> Top posting, this is a very old thread.
>>
>> Keeping in view the recent NetBSD problems and the number of bugs creeping
>> in, I suggest we do
On Fri, Jan 8, 2016 at 12:28 PM, Kaushal M wrote:
> On Fri, Jan 8, 2016 at 12:10 PM, Kaushal M wrote:
> > On Fri, Jan 8, 2016 at 12:03 PM, Raghavendra Talur
> wrote:
> >> Top posting, this is a very old thread.
> >>
> >> Keeping in
On Fri, Jan 8, 2016 at 12:03 PM, Raghavendra Talur wrote:
> Top posting, this is a very old thread.
>
> Keeping in view the recent NetBSD problems and the number of bugs creeping
> in, I suggest we do these things right now:
>
> a. Change the gerrit merge type to fast forward
-Atin
Sent from one plus one
On Nov 10, 2015 11:24 AM, "Kaushal M" wrote:
>
> On Tue, Nov 10, 2015 at 9:24 AM, Raghavendra Gowdappa
> wrote:
> >
> >
> > - Original Message -
> >> From: "Raghavendra Talur"
> >> To: "Gluster
On Tue, Nov 10, 2015 at 9:24 AM, Raghavendra Gowdappa
wrote:
>
>
> - Original Message -
>> From: "Raghavendra Talur"
>> To: "Gluster Devel"
>> Sent: Tuesday, November 10, 2015 3:10:34 AM
>> Subject: [Gluster-devel]
On 11/10/2015 03:10 AM, Raghavendra Talur wrote:
> Hi,
>
> While trying to understand how our gerrit+jenkins setup works, I
> realized of a possibility of allowing bugs to get in.
>
> Currently, our gerrit is setup to have cherry-pick as the submit type.
> Now consider a case where:
>
> Dev1
On Tue, Nov 10, 2015 at 3:10 AM, Raghavendra Talur wrote:
> Hi,
>
> While trying to understand how our gerrit+jenkins setup works, I realized of
> a possibility of allowing bugs to get in.
>
> Currently, our gerrit is setup to have cherry-pick as the submit type. Now
> consider
- Original Message -
> From: "Raghavendra Talur"
> To: "Gluster Devel"
> Sent: Tuesday, November 10, 2015 3:10:34 AM
> Subject: [Gluster-devel] Gerrit review, submit type and Jenkins testing
>
> Hi,
>
> While trying to understand how our
15 matches
Mail list logo