Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change to GIT #379

Open
GoogleCodeExporter opened this issue Dec 15, 2015 · 4 comments
Open

Change to GIT #379

GoogleCodeExporter opened this issue Dec 15, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

Should we think about changing to GIT for version control?
This would greatly improve the options for version/branch control etc.

Also it's worth thinking about changing to Github, on another project I'm part 
of we did the change couple of months ago and the change instantly brought more 
developers as Github has better social network around it. Github also has the 
same basic features and some more (especially better forking support, so we 
could have one "main fork" and each individual would have their own fork with 
the possibility of making own customizations without having them in the main 
branch).

Original issue reported on code.google.com by [email protected] on 21 May 2013 at 1:41

@GoogleCodeExporter
Copy link
Author

Google Code does have GIT support, so we could continue using Google Code also, 
although in my opinion Github would be a better choice (although my own 
preference is Bitbucket :P)

http://code.google.com/p/support/wiki/GitFAQ

Original comment by [email protected] on 21 May 2013 at 1:45

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

Just so you know, I've managed to work around this I-Hate-SVN -problem.

This gives you a clone of current repo to work with:
"git svn clone https://gmapcatcher.googlecode.com/svn/trunk/ gmapcatcher 
--username [email protected]"

Then you can branch etc as you normally do with Git. After you've done changes 
in the branch, just merge/cherry-pick/whatever to the master. Don't forget to 
commit the changes. After this run "git svn dcommit" and they are committed to 
SVN.

To update your git-master from svn, the correct way seems to be to use "git svn 
rebase"

Original comment by [email protected] on 28 May 2013 at 10:43

@GoogleCodeExporter
Copy link
Author

Change to github will certainly bring more cooperation. It's a more active 
platform than google code. 

Original comment by [email protected] on 24 Jun 2013 at 9:16

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant