Re: Automated changes git author
Build Meister? On Wed, Sep 28, 2016 at 1:20 PM, Thomas Weisewrote: > 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 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 > > > Author: CI Support > > > Date: Mon Sep 26 20:36:22 2016 -0700 > > > > > > Fix trailing whitespace. > > > > > > I would suggest we discontinue use of jenk...@datatorrent.com and > start > > > using dev@apex.apache.org instead? > > > > > > Thanks, > > > Thomas > > > > > >
Re: Automated changes git author
BigFoot? On Wed, Sep 28, 2016 at 1:20 PM Thomas Weisewrote: > 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 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 > > > Author: CI Support > > > Date: Mon Sep 26 20:36:22 2016 -0700 > > > > > > Fix trailing whitespace. > > > > > > I would suggest we discontinue use of jenk...@datatorrent.com and > start > > > using dev@apex.apache.org instead? > > > > > > Thanks, > > > Thomas > > > > > >
Re: Automated changes git author
What trustworthy jenkins no more. Kidding aside +1 On Wed, Sep 28, 2016 at 11:34 AM, Thomas Weisewrote: > 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 use of jenk...@datatorrent.com and start > using dev@apex.apache.org instead? > > Thanks, > Thomas >
Re: Automated changes git author
+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 SupportDate: Mon Sep 26 20:36:22 2016 -0700 Fix trailing whitespace. I would suggest we discontinue use of jenk...@datatorrent.com and start using dev@apex.apache.org instead? Thanks, Thomas
Re: Automated changes git author
+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 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 use of jenk...@datatorrent.com and start > using dev@apex.apache.org instead? > > Thanks, > Thomas >
Re: Automated changes git author
+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 -0700 > > Fix trailing whitespace. > > I would suggest we discontinue use of jenk...@datatorrent.com and start > using dev@apex.apache.org instead? > > Thanks, > Thomas >
Automated changes git author
Hi, For changes made by scripts, there has been an undocumented convention to use the following author information (example): commit 763d14fca6b84fdda1b6853235e5d4b71ca87fca Author: CI SupportDate: Mon Sep 26 20:36:22 2016 -0700 Fix trailing whitespace. I would suggest we discontinue use of jenk...@datatorrent.com and start using dev@apex.apache.org instead? Thanks, Thomas