I'm not aware of a way to mark a versioned file such that Subversion won't ever try to commit changes to it. You'd have to manually select (via command-click) your hierarchy of files to exclude the files in question. I think the general pattern to deal with such situations is to create template files (with different names) that are versioned, then create a local customized file which is NOT versioned, and even set it to be ignored so you won't be prompted to add it.
- Quinn On Aug 15, 2013, at 9:10 AM, Rio Brewster <[email protected]> wrote: > I have a couple of files in my local repository that I never want to commit, > but I never want the app to update them either. > > They are essential to the working app, so they are under version control in > the repository, but I have a local version that is set up specifically for > my environment. > > I can't ignore them, and locking them locks them in the repository. > > If there's a way to exclude these files from update. > > > > -- > You received this message because you are subscribed to the Google Groups > "Versions" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/versions. > For more options, visit https://groups.google.com/groups/opt_out.
smime.p7s
Description: S/MIME cryptographic signature
