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

Keeping the Original File at the same State as the Repository

From: Jus Age <jusage_at_live.de>
Date: Tue, 19 May 2015 08:22:42 -0700 (PDT)

Hey everyone,

I'm sure this is kind of a stupid question. I couldn't find anything helpfull except for Local Versioning Systems, which all seem either Command Line based or already outdated.
My question now is, is there a way to get the original Files that I Imported into the Repository also at the same state as the Repository Version?

The problem is, we want to Version some of Config Files of a tool that runs on a Server.
There are several different People accessing this Server with their own accounts. So the Working Space for the Repository will be held in their own Home Directories.

But the problem is that the Software that needs these Config files can only work with them if they are in their Directories, I can't set it up so that it takes them with a file:///, https:// or svn: Link.

I was hoping that the actual File would also be updated when I do a commit, but it seems that Subversion is designed to only keep the Repository in the newest state (which makes sense on the way it is ment to be used).

So is there any way for me to get what I want from TortoiseSVN?

Kind regards and thanks for your help,



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-05-19 17:46:15 CEST

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