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

make rails3 the new master and make master into rails2 #40

Open
grosser opened this issue Oct 13, 2011 · 3 comments
Open

make rails3 the new master and make master into rails2 #40

grosser opened this issue Oct 13, 2011 · 3 comments

Comments

@grosser
Copy link

grosser commented Oct 13, 2011

Paste-friendly :D

git checkout master
git checkout -b rails2
git push origin rails2
git checkout rails3
git branch -D master
git checkout -b master
git push -f origin master
git push origin :rails3

@knzai
Copy link
Collaborator

knzai commented Oct 13, 2011

See my issue in the pull request: #39 If you just isolated the upgrade to 3 into a separate PR (since that pull request will merge into master) I'd merge it. The issue is by doing all the pull requests from the same branch you include all the commits in each one. And you added docs telling people how to use a branch, but the PR will merge rails 3 into master.

Make sense?

@grosser
Copy link
Author

grosser commented Oct 13, 2011

This issue is about changing brynary/master to being rails3 (not releated to my (now fixed) pull-requests)

@halorgium
Copy link

Is this gonna happen? I sadly implemented my own fixes for rails3.
Having a gem released too would be nice!

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

No branches or pull requests

3 participants