This is a question about how people use SVN, in general, not Versions.

I have a lot of projects with a configuration file that has the same format
across all the working copies, but different installation-specific
information filled out in each WC.  I'll never want to commit the changes I
make to the file, but I do want to update it if there's a change made to it
in the trunk.

Sometimes I make a branch only for that file, but merging is annoying... I'd
rather have everything be a WC of the trunk, and just not worry about
committing it accidentally.  Sometimes I don't even want that information in
a branch, like if it contains an API key or database passwords.

Is there some way to mark a file like this as ignored for committing but not
updating?

Thanks,
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to