A Scalable, User-Friendly Source Control System.
Go to file
2008-10-26 22:39:17 -05:00
svnwrap Fix tests against the improved SWIG bindings in Subversion 1.6. 2008-10-18 18:56:09 -05:00
tests Improved handling of copies from outside of trunk. 2008-10-26 22:39:17 -05:00
__init__.py Initial import of hgsubversion into a public repository. 2008-09-30 11:42:52 -05:00
.hgignore Add a small stack of tests that exercise some of the interesting special cases. 2008-10-08 18:17:29 -05:00
fetch_command.py Some more fixes of cases discovered in the melange repo. If anyone knows how I can reproduce a "replaced" state in Subversion, I'd love to be able to make a real test case for this code. 2008-10-26 22:06:13 -05:00
hg_delta_editor.py Improved handling of copies from outside of trunk. 2008-10-26 22:39:17 -05:00
push_cmd.py Some more fixes of cases discovered in the melange repo. If anyone knows how I can reproduce a "replaced" state in Subversion, I'd love to be able to make a real test case for this code. 2008-10-26 22:06:13 -05:00
README Add a segment on running the tests before use. 2008-10-14 09:13:15 -05:00
svncommand.py I meant ambiguous. 2008-10-17 22:48:40 -05:00
util.py Some more fixes of cases discovered in the melange repo. If anyone knows how I can reproduce a "replaced" state in Subversion, I'd love to be able to make a real test case for this code. 2008-10-26 22:06:13 -05:00
utility_commands.py Fix up the rebase docstring to be less vague. 2008-10-15 13:21:59 -05:00

-*-restructuredtext-*-

About
-----
hgsubversion is an extension for Mercurial that allows using Mercurial as a 
Subversion client.

Right now it is *not* ready for production use. You should only be using this if 
you're ready to hack on it, and go diving into the internals of Mercurial and/or 
Subversion.

Installation
------------
You need to have Subversion installed with the SWIG Python bindings.
You need a recent Mercurial. At present, the required memctx code is in mercurial_, crew_, and crew-stable_, but not mercurial-stable. Install Mercurial from one of mercurial or the crew repos if you have not already. Personally, I use crew_. Note that if you have Subversion 1.4, most functionality will probably work, but pushing and using replay (faster than diff) do not, so you should consider upgrading your Subversion installation or wait for the ctypes bindings to be supported.

.. _mercurial: http://selenic.com/repo/hg
.. _crew: http://hg.intevation.org/mercurial/crew
.. _crew-stable: http://hg.intevation.org/mercurial/crew-stable

If you are unfamiliar with installing Mercurial extensions, please see the UsingExtensions_ page in the Mercurial wiki. Look at the example for specifying an absolute path near the bottom of the page. You want to give the path to the top level of your clone of this repository.

.. _UsingExtensions: http://www.selenic.com/mercurial/wiki/index.cgi/UsingExtensions

Before using hgsubversion, I *strongly* encourage you to run the automated tests. Just use nose_ if you have it (or ``easy_install nose`` if you want it), or use ``python tests/run.py`` to run the suite with the conventional test runner. Note that because I use nose, there's a lot of stdout spew in the tests right now. The important part is that all the tests pass.

.. _nose: http://code.google.com/p/python-nose/

Basic Use
-----------
Get a new clone of an svn server::

 $ hg svnclone <svn URI> [destination]

Real example::

 $ hg svnclone http://python-nose.googlecode.com/svn nose-hg

Pull new revisions into an already-converted repo::

 $ hg svn pull

For more information, see 'hg svn help' while in a converted repo.