Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Flume >> mail # dev >> [DISCUSS] Git as primary source control for Flume


Copy link to this message
-
Re: [DISCUSS] Git as primary source control for Flume
+1 for using Git as primary source control system.

Thanks Hari for following up on this.

Regards,
Arvind Prabhakar

On Wed, Jul 11, 2012 at 7:16 PM, Leslin <[EMAIL PROTECTED]> wrote:

>  +1 for this proposal.  Git is fine for me.  I never back to SVN after I
> touched git.
>
> 2012/7/12 Mike Percy <[EMAIL PROTECTED]>
>
> > On Wed, Jul 11, 2012 at 5:45 PM, Ralph Goers <[EMAIL PROTECTED]
> > >wrote:
> >
> > > IMO the person who wrote the code is the one who should get credit.
> > >
> >
> > Of course they should get the credit for the work.
> >
> > Anyone who has ever performed a careful code review knows that it can be
> > time-consuming work. I assume that's one reason why we currently list
> both
> > the author and the committer in the commit message.
> >
> > Regards,
> > Mike
> >
>
>
>
> --
>
>
>
> Best Regards
>
> Leslin
>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB