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

RE: What is pattern syntax for svn:ignore?

From: Dale Worley <dworley_at_pingtel.com>
Date: 2005-02-01 16:59:50 CET

The book implies that an svn:ignore value can contain any relative path name
from that directory, but that seems poorly structured to me and likely to
not be implemented correctly. What has always worked for me is for
svn:ignore to be a set of lines, each of which uses ordinary shell wildcards
to specify names within that directory that will be ignored.

Dale

-----Original Message-----
From: Steve Cohen [mailto:scohen@javactivity.org]
Sent: Monday, January 31, 2005 9:09 PM
To: subversion
Subject: What is pattern syntax for svn:ignore?

The svn book could use more examples on using svn:ignore.

My first several use cases for this did not go smoothly. The book talks
about patterns at several points but the syntax is not explained.
For example, is the **/ notation used in places like Ant supported?
What glob wildcards are supported. Etc. Here was my first use case:

The Gimp tool creates .xvpics directories whenver it edits files. I'm
not sure what they are but I don't want them version controlled. So my
usecase is: Ignore anything in any directory named .xvpics and all its
children, starting from the current directory and all including all its
current children.
What is the pattern?

But beyond answering the question, the answer should hopefully make it
into the book.

Steve Cohen

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 1 17:03:18 2005

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.