Re: Automated changes git author

2016-09-28 Thread Pradeep A. Dalvi
Build Meister? On Wed, Sep 28, 2016 at 1:20 PM, Thomas Weise wrote: > What about the name "CI Support"? Does not look like best fit either. Any > better ideas or keep it? > > I will document the outcome in the contributor guidelines. > > On Wed, Sep 28, 2016 at 11:13 AM, Pramod Immaneni > wrote

Re: Automated changes git author

2016-09-28 Thread Vlad Rozov
Apex Dev? On 9/28/16 13:41, Sandesh Hegde wrote: BigFoot? On Wed, Sep 28, 2016 at 1:20 PM Thomas Weise wrote: What about the name "CI Support"? Does not look like best fit either. Any better ideas or keep it? I will document the outcome in the contributor guidelines. On Wed, Sep 28, 2016 a

Re: Automated changes git author

2016-09-28 Thread Pramod Immaneni
The dev email you suggested for email sounds good. How about "Apex Dev" for name? > On Sep 28, 2016, at 4:20 PM, Thomas Weise wrote: > > What about the name "CI Support"? Does not look like best fit either. Any > better ideas or keep it? > > I will document the outcome in the contributor guidelin

Re: Automated changes git author

2016-09-28 Thread Sandesh Hegde
BigFoot? On Wed, Sep 28, 2016 at 1:20 PM Thomas Weise wrote: > What about the name "CI Support"? Does not look like best fit either. Any > better ideas or keep it? > > I will document the outcome in the contributor guidelines. > > On Wed, Sep 28, 2016 at 11:13 AM, Pramod Immaneni > wrote: > > >

Re: Automated changes git author

2016-09-28 Thread Thomas Weise
What about the name "CI Support"? Does not look like best fit either. Any better ideas or keep it? I will document the outcome in the contributor guidelines. On Wed, Sep 28, 2016 at 11:13 AM, Pramod Immaneni wrote: > What trustworthy jenkins no more. Kidding aside +1 > > On Wed, Sep 28, 2016 at

Re: Automated changes git author

2016-09-28 Thread Pramod Immaneni
What trustworthy jenkins no more. Kidding aside +1 On Wed, Sep 28, 2016 at 11:34 AM, Thomas Weise wrote: > Hi, > > For changes made by scripts, there has been an undocumented convention to > use the following author information (example): > > commit 763d14fca6b84fdda1b6853235e5d4b71ca87fca > Aut

Re: Automated changes git author

2016-09-28 Thread Vlad Rozov
+1 and making it a documented convention. Vlad On 9/28/16 08:34, Thomas Weise wrote: Hi, For changes made by scripts, there has been an undocumented convention to use the following author information (example): commit 763d14fca6b84fdda1b6853235e5d4b71ca87fca Author: CI Support Date: Mon Se

Re: Automated changes git author

2016-09-28 Thread Aniruddha Thombare
+1 on switching from jenk...@datatorrent.com. Is it possible to have c...@apex.apache.org? Or no-reply@apex...? Thanks, A _ Sent with difficulty, I mean handheld ;) On 28 Sep 2016 9:04 pm, "Thomas Weise" wrote: > Hi, > > For changes made by scripts, there

Re: Automated changes git author

2016-09-28 Thread David Yan
+1 On Sep 28, 2016 8:34 AM, "Thomas Weise" wrote: > Hi, > > For changes made by scripts, there has been an undocumented convention to > use the following author information (example): > > commit 763d14fca6b84fdda1b6853235e5d4b71ca87fca > Author: CI Support > Date: Mon Sep 26 20:36:22 2016 -07

Automated changes git author

2016-09-28 Thread Thomas Weise
Hi, For changes made by scripts, there has been an undocumented convention to use the following author information (example): commit 763d14fca6b84fdda1b6853235e5d4b71ca87fca Author: CI Support Date: Mon Sep 26 20:36:22 2016 -0700 Fix trailing whitespace. I would suggest we discontinue us