hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vikas Parashar <vikas.paras...@fosteringlinux.com>
Subject RE: [DISCUSS] Migrate from svn to git for source control?
Date Sun, 03 Aug 2014 06:46:54 GMT
+1.. Now git is more handy. We can easily switch between the branches. As
we all know, LINUX kernel is on same and well managed.

We can all have own local repo and can commit to stream once we will
connected to web.
On 3 Aug 2014 12:09, "Liu, Yi A" <yi.a.liu@intel.com> wrote:

> +1, Git is more convenient for development and we can switch easily
> between branches and can have local branches.
>
> Regards,
> Yi Liu
>
>
> -----Original Message-----
> From: Karthik Kambatla [mailto:kasha@cloudera.com]
> Sent: Saturday, August 02, 2014 7:44 AM
> To: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
> mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
> Subject: [DISCUSS] Migrate from svn to git for source control?
>
> Hi folks,
>
> From what I hear, a lot of devs use the git mirror for development/reviews
> and use subversion primarily for checking code in. I was wondering if it
> would make more sense just to move to git. In addition to subjective liking
> of git, I see the following advantages in our workflow:
>
>    1. Feature branches - it becomes easier to work on them and keep
>    rebasing against the latest trunk.
>    2. Cherry-picks between branches automatically ensures the exact same
>    commit message and tracks the lineage as well.
>    3. When cutting new branches and/or updating maven versions etc., it
>    allows doing all the work locally before pushing it to the main branch.
>    4. Opens us up to potentially using other code-review tools. (Gerrit?)
>    5. It is just more convenient.
>
> I am sure this was brought up before in different capacities. I believe
> the support for git in ASF is healthy now and several downstream projects
> have moved. Again, from what I hear, ASF INFRA folks make the migration
> process fairly easy.
>
> What do you all think?
>
> Thanks
> Karthik
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message