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

RE: stumped by where svn:ignore is stored...

From: Karan, Cem \(Civ, ARL/CISD\) <CKaran_at_arl.army.mil>
Date: 2004-12-14 23:42:55 CET

> On Tue, 14 Dec 2004 16:35:09 -0500, Karan, Cem (Civ,
> ARL/CISD) <CKaran@arl.army.mil> wrote:
> > > Had you seen svn proplist --verbose ? That will also
> list property
> > > contents. svn propget svn:ignore TARGET will also do it for you.
> >
> > Just tried it, but it doesn't find svn:ignore in any revision.
> >
> > > Now, you might want to check ~/.subversion to see if your
> > > configuration has a default exclude with .DS_Store in it. That
> > > might be the case...
> >
> > Just checked; my global-ignores variable is commented out.
>
> Correct. If you don't provide one, the one you see (which is commented
> out) is the hard coded default.

That would explain it, but IIRC, I had to set this at one point; did this default behavior come about sometime between SVN 1.0.9 and 1.1.1? Thats the only thing that I can think of...

Note that I'm not complaining about this behavior! Quite the opposite in fact; SVN did what I wanted without my having to think about it; I was just surprised and was trying to dig into where all the info was stored at.

> (I believe ~/.subversion/config states so.)

In my file at least it doesn't; it just states that if you uncomment the line then those files are ignored. My assumption is that with that line commented out NOTHING is ignored. I can see the .svn directories being ignored, but if there are files outside of those directories being ignored...it could lead to some very interesting times.

Thanks,
Cem Karan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 14 23:45:14 2004

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.