A Scalable, User-Friendly Source Control System.
Go to file
2008-11-05 13:37:08 +01:00
svnwrap push_cmd: handle copies at file level 2008-11-05 13:37:08 +01:00
tests test_fetch_renames: test directory copy with children files changed in-between 2008-11-05 13:37:08 +01:00
__init__.py svnclone now updates to the tip revision if it is the initial clone. 2008-11-01 13:40:19 -05:00
.hgignore Ignore coverage information. 2008-11-06 09:23:49 -06:00
fetch_command.py Added some coverage pragmas to stop it from trying to cover things we can't test. 2008-11-06 09:47:42 -06:00
hg_delta_editor.py hg_delta_editor: make branches_in_paths() return the branch svn path too 2008-11-05 13:37:08 +01:00
push_cmd.py push_cmd: handle copies at file level 2008-11-05 13:37:08 +01:00
README crew-stable does not have what I need after all. Oops. 2008-11-01 13:50:46 -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 Add an hg svn info subsubcommand that prints out what you would expect from svn info. 2008-11-07 15:02:00 -06: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 from Subversion 1.5 or later.
You need a recent Mercurial. At present, the required memctx and rebase code is in mercurial_ and  crew_, but not crew-stable_ or mercurial-stable_. Install Mercurial from one of mercurial or crew if you have not already. Personally, I use crew_.

.. _mercurial: http://selenic.com/repo/hg
.. _mercurial-stable: http://selenic.com/repo/hg-stable
.. _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.