>I hope I guessed right what you meant.
Yes, you did :)
> 1. You create a solution on top of SVN.
> This means e.g. writing a batchfile that creates or syncs a WC with the
> according configuration file. You might also be able to employ symlinks or
> other features of your filesystem to your advantage.
OK, I thought about that also.
For example to write a script, which would copy the
configuration file to my working copy at the time my PC starts up.
>
> 2. You turn the directory where the file is stored a working copy.
> You can do so by simply creating a target dir in the repository ("svn
> mkdir
> $URL/config") and checking out that dir in the directory where the file is
> stored ("svn co $URL/config ."). You can then add the configuration file
> and
> commit, just like with any other WC.
>
Hmm, that would imply going to this configuration directory each
time I want to commit, right? What I am searching for is a solution
where I commit one single time in the working copy of my project and
do not care about the rest.
> I believe there also was a script or so to upload a single file to a
> repository, which might be a third alternative.
>
That's interesting. Do you know anything about this script?
BR
Ewgenij
