Moving from One Hg to Another

Peer Sommerlund peer.sommerlund at gmail.com
Tue Nov 25 05:52:43 UTC 2008


2008/11/24 Benjamin Johnson <benjamin.johnson at timco.aero>

> That sounds like it would work if I were creating a new common repository
> --  but what about the more likely case that I am just moving some code out
> to a more global repository?  Isn't there an easy way to maintain copy the
> source (w/ history) over?  Then I could simply delete it from the first
> project.


I'm not entirely sure what you would like to achieve, but common
repositories sounds like a job for the forest
extension<http://www.selenic.com/mercurial/wiki/index.cgi/ForestExtension>to
me. In my mind this makes sense even without transferring the history.

>
>
> I like Hg so far, and want to get our team off SVN, but this is a feature
> will be a stumbling block for them.  Perhaps some combination of
> diff/import/export would get the job done?


Maybe it would be clearer what your needs are if you described the SVN
procedure that does this operation.


Regards,
Peer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20081125/fea840f6/attachment-0001.html>


More information about the Mercurial mailing list