On Thu, Dec 4, 2008 at 06:28, Eli Gibson <eli.gibson_at_gmail.com> wrote:
> I have a configuration file that holds local settings, which may be
> different for every working copy (mostly absolute paths that vary from
> machine to machine). I would like to have a template stored in the
> repository. When the repository is checked out, the user will get the
> template, and make modifications that are machine specific. However, I
> do not want these changes to be commited back over top of the template
> accidentally.
> I was hoping that adding a matching svn:ignore pattern to the
> directory containing the configuration file would prevent the changes
> from being committed, but that didn't seem to work. Should this have
> worked (i.e. did I just do it incorrectly), or if not, is there a
> better solution for the problem?
You can't svn:ignore something that's presently versioned because
you've already told Subversion you want to version it.
What you have described here is an almost verbatim copy of an entry in
the FAQ. http://subversion.tigris.org/faq.html#ignore-commit
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=979662
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2008-12-04 16:26:18 CET