[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Re: Feature request: ignore-on-commit setting in repository

From: Andy Levy <andy.levy_at_gmail.com>
Date: Tue, 9 Nov 2010 08:47:59 -0500

On Tue, Nov 9, 2010 at 04:57, Jaap Taal <jaap_at_q42.nl> wrote:
> You guys missed my point, gonna try to explain it again:
> On checkout I want a fully functional working setup.
> This is the most important thing.
> Because I want a working setup right after checkout, I need to add every config file to svn.
> However, if I would change a database connectionstring or the sample sqlite db file by using my application, I don't want these changes to be committed: that's why we use the ignore-on-commit changelist which is already present in TSVN.
> Obivously when a new connectionstring comes up in the config file and the code reflects this I will revert to the default repository version of my config file and commit this (changes will be an appended line). Typically this will merge just well...

I solve this by making my applications and/or their build processes
intelligent enough to know what configuration is required, either at
compile- or run-time. All my configurations are stored in the
repository, and I use the Configuration Manager/Web Deploy Projects in
Visual Studio to do it at compile time, and a home-grown method for my
Java app.


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

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.