Showing results for 
Search instead for 
Did you mean: 

maintaining code in two labview versions

You're right, it is quite possible (and even likely) that the thumbs.db file is only created when you view the directory as thumbnails, but that was just an example.

The point was that you could have unexpected things cause changes in your directories and then you "need" to commit.

The way to avoid that is to set the ignore property, but setting a property on a hierarchy overwrites your previous properties and you can't ignore those files which you already versioned.

Try to take over the world!
0 Kudos
Message 11 of 12

tst wrote:

P.S. What do you do for managing the DB (managing users and passwords, backing up, etc.)? Do you use the SVN commands or did you write some wrapper UI VIs around that? I'm still in the process of finalizing that aspect here (and I need to finish writing my own internal use document), so I would like to hear any tips you might have.

We are using now for 3.5 years. The repository resides on a Linux box using the filesystem storage backend. To backup I used a script found in the subversion book. Actually it is doing a dump each evening of the new revisions. A dump has the advantage that you can easily migrate to new svn versions with format changes (doing the dump than would take very much time) but it is not the most efficient way to backup (with the filesystem storage a copy should work as well). This happens all as a cronjob on the Linux server.

The users are actually not managed separately but are authenticated in our Windows 2000 domain. To do this I use a winbind setup on the Linux server. As we are just a few developers there are no additional restrictions set (yet). At end-user level we use the excellent TortoiseSVN.

0 Kudos
Message 12 of 12