Advertisement
Guest User

Untitled

a guest
Feb 8th, 2016
61
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.30 KB | None | 0 0
  1. 1. clone our fork: git clone git@github.com:IPnett/puppet-keystone.git
  2. 2. add upstream remote: git remote add upstream git@github.com:openstack/puppet-keystone.git
  3. 3. git remote update
  4. 4. in case our fork has become lobotimzed and had branch switched, get master: git checkout -t -b master origin/master
  5. 5. update master from upstream: git merge upstream/master
  6. 1. i had to do git merge -s recursive -Xtheirs upstream/master
  7. 2. git push
  8. 6. sync stable/kilo if it exists in our fork:
  9. 1. git checkout -t -b stable/kilo origin/stable/kilo
  10. 2. git merge -s recursive -Xtheirs upstream/stable/kilo
  11. 3. git push
  12. 6. get new branch stable/liberty from upstream: git checkout stable/liberty
  13. 1. push it to fork branch: git push --set-upstream origin stable/liberty
  14. 7. now, for the roll-forward of our local changes:
  15. 1. branch ipnett_liberty off of stable/liberty: git checkout -b ipnett_liberty stable/liberty
  16. 2. merge our kilo changes into liberty: git merge ipnett_kilo
  17. a) i ran into weird conflicts, somehow the ipnett fork has had its history munged, and instead I did: git merge -s recursive -Xours origin/ipnett_kilo, which let upstream code prevail in the history conflict. i checked that the in this case single locally kept commit was applied, and it was.
  18. 3. resolve conflicts
  19. 4. git commit
  20. 5. git push
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement