commit to the wrong branch what to do
Bryan Murdock
bmurdock at gmail.com
Thu Sep 1 13:24:17 UTC 2016
If you haven't pushed the wrong commit yet (it exists only in your local
clone) you can just rebase it:
hg rebase -s <wrong-branch> -d <correct-branch>
Bryan
On Sep 1, 2016 3:16 AM, "Uwe Brauer" <oub at mat.ucm.es> wrote:
Hi
Most likely this sometimes happens:
I added, removed, edited and then commit, but alas to the wrong branch.
What is the most efficient way to solve this issue?
I did it completely manually.
hg update wrong-branch
copied the files in question to another place.
hg update correct-branch
Copied the correct files, and moved out the not needed files.
hg commit -m "repaired"
hg update wrong-branch
Copied the files
hg commit "back to the wrong branch"
Maybe a patch would have been the simpler solution?
_______________________________________________
Mercurial mailing list
Mercurial at mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20160901/84199e60/attachment-0002.html>
More information about the Mercurial
mailing list