Newbie question: Svn and Unison

I'm just getting started with Subversion and I've read most of the book.
   Would appreciate any guidance on this ...

I develop software at 3 locations. Currently I have a large working
folder with lots of project folders inside. Some of the projects are
active and others are dormant.

I've been using Unison to keep my working folder updated back to my
Linux server and across the 3 stations. I have a script file so "one
click" will run the Unison sync function to upload/download changes.
Mostly this works fairly well.

Should I get rid of the Unison scheme altogether in favor of pure Svn or
just use Svn on top of the working folder that is being kept up by Unison?

I've been influenced by that article "Keeping your Life in Subversion"
but have some reservations.

What happens if I write a script that mindlessly does 'svn update' on
each project folder even tho that project hasn't been touched? Does it
create lots of meaningless intermediate versions or does it just skip it
if the project has no changed files?

Any other big gotcha's with using a mindless script that runs 'svn
update' across a bunch of folders?

All thoughts and guidance appreciated.

Thanks,
Michael

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 13 20:29:35 2005