pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jarek Jarcec Cecho <jar...@apache.org>
Subject Re: Move pig project from svn to git repository
Date Sun, 03 Feb 2013 21:54:05 GMT
Hi Bill,
thank you very much for your feedback. Mostly in the past the synchronization did not seemed
reliable and sometimes it took couple of hours or days to get latest updates from from svn
to the git mirror. Also even recently, sometimes the mirrors seems unresponsive. At least
for me. I'm not experiencing such issues when I'm working with the projects that are primarily
running on git. Thus I was wondering whether pig community would be open to such migration.


On Fri, Feb 01, 2013 at 10:38:00PM -0800, Bill Graham wrote:
> I'm a huge fan of git and use it exclusively for Pig with the exception of
> committing patches. I haven't personally experienced any reliability issues
> with the git mirror. What are the reliability issues you've seen?
> On Fri, Feb 1, 2013 at 6:46 PM, Jarek Jarcec Cecho <jarcec@apache.org>wrote:
> > Hi pig developers,
> > I personally prefer git over svn, so I'm using the git mirrors that Apache
> > provides. As those mirrors do not seem entirely reliable I was wondering
> > whether there are other pig developers that also prefer git over svn as
> > myself. Apache Infrastructure Team is supporting projects that are
> > primarily working with git, so my question is - would pig developer
> > community be interested in migrating the repository from svn to git?
> >
> > I've recently participated in three projects that done this change, namely
> > Sqoop, Flume and MRunit, and it's not a big deal. The process is rather
> > simple, just it take some time as most of the job is done by Infrastructure
> > team. I would be more than happy to help or even drive the process in case
> > that this change would be desirable by community.
> >
> > Jarcec
> >
> -- 
> *Note that I'm no longer using my Yahoo! email address. Please email me at
> billgraham@gmail.com going forward.*

View raw message