You could have a file called copy-me-as-config.txt, which would serve as the un-filled out template config file under version control with no sensitive information in it.When you change how the system works, you would commit changes to copy-me-as-config.txt, and if that file ever changed, you would merge the changes into your config.txt file so the system would work with the new changes you made to the config.
In order to not accidentally commit sensitive details, yo commit the property "svn:ignore config.txt" on the folder containing copy-me-as-config.txt and config.txt. This makes it so the config.txt file is overlooked by svn, so it won't accidentally be added. Does that make sense? -Ray --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/versions?hl=en -~----------~----~----~----~------~----~------~--~---
