On Tue, May 19, 2015 at 10:22 AM, Jus Age <jusage_at_live.de> wrote:
>
> 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?
>
>
I guess, if you're going to do this with SVN, that you want a tool that
monitors the repository for changes, and when it sees a change, allows you
to specify an action to take (for example, running `svn update` on a
working copy to pull in the changes, or downloading individual files with
`svn cat`).
Commit Monitor is one such tool, designed to work with TortoiseSVN. If you
wait until version 1.9 comes out, I understand a similar tool is integrated
into TortoiseSVN.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3118371
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-05-20 17:03:42 CEST