Advice/Examples for dealing with existing SVN with externals

[Steve Barnes]

Hi All,

I am trying to put together a plan for dealing with the following situation:
1/ Set of existing projects currently managed under SVN,
2/ At least one of them uses several of the others as svn:externals,
3/ There is a considerable history that we would need/like to retain,
4/ There are numerous branches which will need to be developed/maintained.
5/ Remote repository server currently does not support hg, (but does 
support svn and git).

The sort of structure that I am envisaging at the moment is:
Envisioned Structure
The bit I am struggling with is the mechanism for connecting the 
sub-repositories in to the required developer structure, where the svn 
externals were.  If all the developers were running linux then I could 
use a script to put soft links in place as a possible solution but 
they/we are all running Microsoft Windows, (a mix of XP and 7).

Does anybody have any advice/examples - searching the web is resulting 
in contradictory results including it can/can't be done, it does/doesn't 
need forest, some other extension, etc.
-- 
Steve /Gadget/ Barnes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20130108/c1d1771a/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: HG_SVN_Envision.png
Type: image/png
Size: 112029 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20130108/c1d1771a/attachment-0002.png>