+1

Thanks,
Prashanth.

From: abhijeet gaikwad [mailto:[email protected]]
Sent: Wednesday, August 08, 2012 11:27 PM
To: [email protected]
Cc: [email protected]
Subject: Re: [VOTE] Moving source control from svn to git


+0
Am good with any.

Thanks,
Abhijeet
On 8 Aug 2012 23:05, "Kathleen Ting" 
<[email protected]<mailto:[email protected]>> wrote:
+1
On Wed, Aug 8, 2012 at 1:33 AM, Cheolsoo Park 
<[email protected]<mailto:[email protected]>> wrote:
+1

On Wed, Aug 8, 2012 at 12:41 AM, Alex Newman 
<[email protected]<mailto:[email protected]>> wrote:

+1

Sorry for the tenseness.
My large fingers Swype Android poorly.
Alex Newman
4045076749<tel:4045076749>
On Aug 8, 2012 12:38 AM, "alo alt" 
<[email protected]<mailto:[email protected]>> wrote:
+1

- Alex

Jarek Jarcec Cecho wrote:


I would like to propose moving our repository from SVN to GIT (everything will 
still be handled by Apache, it's just repository format change). Apache 
Infrastructe team requires one volunteer from the project to actively 
participate in that process and I would like to volunteer myself.

Please vote

[] +1 Yes - Sqoop should move to GIT and Jarcec should be the volunteer
[] +0 Abstain - I don't have a preference
[] -1 No - Sqoop should not move to GIT



Jarek Jarcec Cecho<mailto:[email protected]>
August 8, 2012 8:46 AM
I would like to propose moving our repository from SVN to GIT (everything will 
still be handled by Apache, it's just repository format change). Apache 
Infrastructe team requires one volunteer from the project to actively 
participate in that process and I would like to volunteer myself.

Please vote

[] +1 Yes - Sqoop should move to GIT and Jarcec should be the volunteer
[] +0 Abstain - I don't have a preference
[] -1 No - Sqoop should not move to GIT

--
Alexander Alten-Lorenz
http://mapredit.blogspot.com
German Hadoop LinkedIn Group: http://goo.gl/N8pCF



______________________________________________________________________
Disclaimer:This email and any attachments are sent in strictest confidence for 
the sole use of the addressee and may contain legally privileged, confidential, 
and proprietary data.  If you are not the intended recipient, please advise the 
sender by replying promptly to this email and then delete and destroy this 
email and any attachments without any further use, copying or forwarding

Reply via email to