[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn:ignore

From: Ryan Schmidt <subversion-2006Q1_at_ryandesign.com>
Date: 2006-04-21 16:58:19 CEST

On Apr 21, 2006, at 16:12, Simon Whittaker wrote:

> I would like to ignore a whole directory from any changes made by
> the developers, we are using tortoisesvn on the checkout end and
> from what I understood you could use the properties and svn:ignore
> to ensure that the directory was left out. I have set svn:ignore to
> * and set recursive but the changed files are still appearing when
> I commit. I think I am probably misunderstanding the process here
> but would appreciate any guidance.

Sounds correct to me. If you have a directory "foo" and you want it
to be in the repository, but empty, such that any files a developer
has locally in "foo" do not get shown as unversioned when using svn
status, then this is the way to go.

svn propset svn:ignore '*' foo
svn commit -m "Ignoring the contents of 'foo'."

Note that if you had already added items in the directory and
committed them, then yes, changes in those files will continue to
show up in "svn status". You can "svn remove" them if you like, to
remove them from the repository now.

If, on the other hand, you don't want the directory itself in the
repository, you would not "svn add" it, and you would instead set the
"svn:ignore" property of the parent directory to "foo".

svn propset svn:ignore foo .
svn commit -m "Ignoring any item 'foo' in this directory."

And again, if you were converting from the former approach to the
latter, you would first have to "svn remove" the foo directory from
the repository.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 21 17:03:07 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.