version control - How do I use Mercurial to merge in changes made outside the repository? -
I joined the team with Greenfield Code. When I joined, they did not have a normal store, and they emailed me their latest tarball (yes, I know ...) I'm closing the torb, making changes and adding files I am Now there is a Mercurial repository (Hooray!) In the team, and it remains with the same code that includes the recent changes made by other people. In other words, I have the original Tarbald Code directory, my changes in my directory, and the third directory has an HG clone, where the original turbaded code is the common ancestor.
What's the best way to merge my changes in the Mercurial repository? There is no history of seasonal general ancestor. I am a new brand for mercury. My VCS experience is with CVS, Prabal, and some SVN. Can I create two more local HG clones and rewrite one with the original code Can I do the other with my changed code, and to merge mercurial in any way? (And if so, how?) Or should I consider using a free merge tool and then copy the merged version to its clone directory? or something else?
All this is on RHE Linux.
Thank you.
An alternative to try is something like this:
diff - UrN Your original-tarball is your current code & gt; Mychanges.patch hg import your current-repo your local local clone CD to your local clone hg update -r # # import hg imported into history - no-commit../mychanges.patch # check this HG Commit- M 'my change' # and lieutenant; You will be warned that new heads will merge HG # merge your changes with your changes because they start using the successor HG Commitment - it is taking all your work to this day, As importers are based on the old revision, and after that their work is dissolving, they started using it after starting work in the workplace. Gave. Ideally they have a R. wire that they gave to you, but there is a hope that it is not very different.
Comments
Post a Comment