Hello, On Fri, 03 Apr 2009, Raja Subramanian wrote: > I've been planning on setting up a central SVN repository off-site so that > my users can commit their changes daily, and thus do their own backups. > And something like TortiseSVN should ease the end user experience.
As long as your users are happy, things are fine. All the same, version control is not quite the same as backup! In particular, you will need to backup your subversion server side. > Any idea if mercurial or other will work better for my requirement? Note that subversion tends to duplicate space usage. I think that git (and mercurial) avoids this. What VCS does is that it reduces the need for user backups to have long storage times: If you can restore your recent VCS data correctly it already contains all the older files. Anything that creates data cumulatively has this advantage. One thing that VCS's tend to fail at is file modification times and file modes. You need to save those independently. For example, there is 'etckeeper' which maintains '/etc' using git. Regards, Kapil. -- _______________________________________________ To unsubscribe, email [email protected] with "unsubscribe <password> <address>" in the subject or body of the message. http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
