Hi Richard,
On 19 April 2011 10:29, Richard M Willis <RichardW_at_pulsar-pm.com> wrote:
> My development environment has a project file which change frequently for trivial reasons. It's basically an .ini file with all the source files listed and all the compiler options etc, but it also has ephemeral stuff in it, such as "time of last compile", "size of last window opened", "10 previous search results". That sort of stuff.
>
> This file is changing all the time and only part of it needs to be put under version control.
>
> I am told that I need to templatise the file. I did this and now have an init.bat script to copy said template to the real file; I have a corresponding script, outit.bat, which copies (just) the important stuff back to the template file. In this way, if only ephemeral stuff has changed, (T)SVN sees this file as unchanged, which is what I want.
>
> This init/outit scheme works fine, but having to do it manually on every checkout/update, and before every "check for modifications" is a pig.
>
> The set of hooks provided is very minimal. I need something like a "post-checkout","post-update" script, and a "pre-check-for-modifications" script.
>
Take a look at client side hook scripts:
http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-settings.html#tsvn-dug-settings-hooks
--
Regards,
Jean-Marc
--
. ___
. @@ // \\ "De Chelonian Mobile"
. (_,\/ \_/ \ TortoiseSVN
. \ \_/_\_/> The coolest Interface to (Sub)Version Control
. /_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2721336
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-04-19 12:33:17 CEST