Being a Python-whore, I obviously picked Mercurial. Here's a little memo with what I've done, mostly following the page on the Mercurial wiki dedicated to Subversion interop. Note that this may not be the optimal solution, it's a work-in-progress:
- enable the MQ extension in .hgrc or Mercurial.ini
- check out the original Subversion repository
- in the checked-out copy, do
hg init
- in the same place, create a file called .hgignore, listing the files we don't want to track; typically, this means the .svn/ directory and .hgignore itself
- add all the files to Mercurial:
hg ci -Am "Original svn checkout"
- initialize MQ:
hg qinit -c
- if you have existing patches, you want to start applying them now. If they create new files, you'll need to "hg add" them
- when you want to save state, use
hg qnew -f mynewpatch
This will create a patch called "mynewpatch" in the MQ stack, listing differences with the original version, and it will consider it as applied.
This comment has been removed by the author.
ReplyDeleteUh, nice, I didn't know about hg command abbreviations. You learn something every day.
ReplyDeleteWell, let us know how it goes. Somehow, I feel a certain amount of inertia to overcome in the whole process.
Also, uhm, now that I learned a bit about MQ, I wonder why it is called "Queues" since, as far as I understood, it uses a data structure with stack semantics.
ReplyDelete