AFAIK master isn't special, it's just a branch like any other. So there should be no issue in you re-pointing it to the head of A. I think you should be able to just do the following (untested):
git checkout master
git rebase --hard A
and then master will point to the same commit as the head of A. You can also do this using a gui with gitk. Checkout master, launch gitk, right-click on the commit that A points to, and choose 'reset master branch to here'.
On Wed, Sep 22, 2010 at 9:31 AM, elmo <[address removed]>
Here's a git question for ya'll.
I've got a repo that manages a bunch of branches.? For the sake of clarity, let's say my repo has these branches:
The 'master' branch has be neglected for so long, that its? no longer relevant.? What I'd like to do is essentially copy 'A' to master.? I don't want to merge, I want to replace.
In unix terms, I'd like to:
cp -R A master
?For all intents and purposes, A is the new master.
One though I had would be to
1. delete the 'master' branch (git branch -D master)
2. recreate it by branching from A.? ( git branch A)
Is there any harm in me doing this?? Is there anything? special about 'master' that would prevent me from deleting
it?? Or is 'master' just a branch like all others?
Please Note: If you hit "REPLY
", your message will be sent to everyone
on this mailing list ([address removed])
This message was sent by elmo ([address removed]) from San Francisco MongoDB User Group
To learn more about elmo, visit his/her member profile
To unsubscribe or to update your mailing list settings, click here
Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]