On Sat, Sep 13, 2008 at 06:43, Benjamin Buch <benni.buch_at_gmx.de> wrote:
> I'd like to exclude a settings-file in my working copy from being versioned.
> I guess this is a common task... ;-)
>
> The original settings-file for deployment is versioned, so after a checkout
> I have it in the working directory.
> I just don't want to submit any changes I make on the settings-file.
>
> What I did was:
>
> svn propset svn:ignore 'settings.py' .
>
> a 'svn propget svn:ignore .' gives me 'settings.py', so I thought this file
> would be ignored.
> But when I make changes to settings.py in my working directory, 'svn status'
> gives me
>
> M settings.py
>
> , so subversion knows settings.py has been modified, and the modifications
> will be submitted at the next commit.
>
> Now I'm a little confused...
> I thought svn would ignore settings.py?
Once an item is versioned, Subversion will not ignore it.
Your use case is so common it's in the FAQ.
http://subversion.tigris.org/faq.html#ignore-commit
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-13 12:50:41 CEST