[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Repository migration between different access methods

From: el_es <el.es.cr_at_gmail.com>
Date: Wed, 2 Sep 2009 12:47:43 +0000 (UTC)

I am about to migrate the repository of SVN, created with Tortoise, to a
Linux-based server (running Ubuntu Intrepid).
Which method is better (after setting server access and paths that is) :

1) copy the repository files from the Windows machine to where I want to have
them served (it is the native FS it's created on the current host) on the Linux
2) set up server access in Tortoise and use it to import project(s) to the Linux
server ?

The repository so far only hosts projects written by one man (me and my
predecessor, but not at the same time) and now I need to set it up so another
man can access it, preferably preserving the history - so the import is probably
preferred? If the copy method could work, I'd probably need to run svn files via
dos2unix (for cr-lf conversion) ? (the project(s) files however, are supposed to
be Windows only)

After the migration, I will only use server connection (will not use the local
repository any more)

Of course I could do just import the project from working copy, or from export;
effectively zeroing the history, but that would probably be the lats thing I
want to do.

Anybody ever done that ? Pointers? (I searched the group over for 'migration'
(yay for gmane.org search engine)

Btw, which method of access is :
-faster at local network level (comparable to samba file transfer) (I gather,
- secure at the outside access (Webdav over https?)
at the same time ?
- easier to set up than svn:+ssl (WebDAV+https?)
Am I thinking correctly here ?

Thanks in advance,
Best Regards


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-09-02 14:57:27 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.