Why is it checked into SVN if you don't want to version it?
I would think this sort of thing is better handled by taking the
original file, copying it to a unversioned location, and then making
your local mods. You could make that process a simple script that is
also kept and versioned in SVN.
--joe
Walden H. Leverich wrote:
> We've got several files in our web application (web.config and
> settings.xml in our case, in Java it would be a .properties file) that
> we need to change the contents of based on the local machine we're
> installed on. For example, one of the things in settings.xml is the
> path on the local machine to store attachments uploaded through the
> application.
>
> I'm looking for a way to tell svn that changes to a particular file
> aren't to be committed when I do my commits. This could be an svn
> thing, or a TortoiseSVN thing since that's out interface.
>
> snv:ignore doesn't seem to accomplish this. I'm thinking of something
> along the lines of an svn:ignore-content-changed type flag which would
> tell svn to ignore this file and not commit it if the content changed.
> If a property changed then commit the property change. The result
> would be if we did ever want to commit a change, we'd remove the flag,
> make the change, and add back the flag.
>
> Am I missing something obvious? Any suggestions?
>
> -Walden
>
> --
> Walden H Leverich III
> Tech Software
> (516) 627-3800 x3051
> WaldenL@TechSoftInc.com
> http://www.TechSoftInc.com <blocked::blocked::http://www.techsoftinc.com/>
>
> Quiquid latine dictum sit altum viditur.
> (Whatever is said in Latin seems profound.)
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 7 01:37:15 2006