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

Re: Keeping a file under SVN control but preventing it to update locally

From: Andy Levy <andy.levy_at_gmail.com>
Date: Wed, 1 Jul 2009 10:06:02 -0400

On Wed, Jul 1, 2009 at 09:04, Ernesto<petruzanautico_at_yahoo.com.ar> wrote:
> Hi, I hope this is the place to post this, if not, sorry!
>
> What I want is the tipical configuration file, that must be under SVN
> control so I get it when Checking out a repository.
> But what I get is more a template than a real config file.
> Then I have to fill it with my local configuration.
>
> I've seen the approach of naming the file something like
> "config.ini.template" in the SVN repository, but the actual config file
> should be renamed to config.ini
>
> The thing is whoever created the repository didn't name it that way, so,
> what I want is this:
> Marking the file in TortoiseSVN in a way that it doesn't get updated
> when I update its folder, but the file doesn't get deleted on the
> repository.
> In other terms, can I mark a file so it's downloaded on only Checkout
> but never on updates?
> And it also should be out of any commit.

Why not just rename things so that they do match the recommended
approach you're already aware of? You won't lose history.

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

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-07-01 16:06:24 CEST

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.