Re: Need to check a file out, but want never to check it back in !

On 5 Nov 2010, at 09:23, Richard M Willis wrote:

>>
>> .. One question remains: Why not commit the changes
>> anyway? It doesnt hurt anything, does it? At least if you're the sole
>> developer ...
>
> The act of comitting the changes does not harm anything, no.

The thing is, if you have a file for which no changes should be committed, then that file is not a file that should be under version control in the first place. End of story.

The real problem is that when you check out a clean copy of your version controlled tree, the tool chain won't run because it is not clever enough to create its config files if they are not there.

It's easy to create a script that copies a set of templates to the config files if they do not exist. It's easy to put that script and the templates in subversion and if you can't find a way to automate the running of the script on checkout, it's easy to have a .bat file that invokes it in the top level of the project tree that you can just double click once the check out had finished.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2679161

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-11-05 15:05:48 CET