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

RE: Re: ignore list

From: Gerald Britton <gerald.britton_at_gmail.com>
Date: Tue, 8 Nov 2011 13:28:12 -0800 (PST)

> On 08.11.2011 21:23, Gerald Britton wrote:
> >> On Nov 8, 2011, at 2:10 PM, Gerald Britton wrote:
> >>> Sure, but still if I have this one line:
> >>>
> >>> *.foo.* *.vshost.*
> >>>
> >>> the manifest file is *not* ignored. But, if I split it onto two lines:
> >>>
> >>> *.foo.*
> >>> *.vshost.*
> >>>
> >>> _Then_ it _is_ ignored. Just seems odd and hard to figure out.
> >>
> >>
> >> Ah, I had missed that... as the documentation at http://svnbook.red-bean.com/en/1.6/svn.advanced.props.special.ignore.html says, "When found on a versioned directory, the svn:ignore property is expected to contain a list of newline-delimited file patterns that Subversion should use to determine ignorable objects in that same directory."
> >>
> >> You're not supposed to put multiple patterns on a single line in svn:ignore. I guess it's a bit confusing though, since the global ignore pattern (e.g., TSVN's Settings dialog, or in the SVN config file, *does* have multiple patterns on one line.
> >
> > Aha, so we need to hear from the boss on this one. When editing the svn:ignore property in tortoise, is a newline required between the entries or not?
> For svn:externals, yes: all entries must be on a new line.

OK -- I changed my ignore list to one entry per line. It now looks like:


However, when I do a SVN Commit on this directory, it still shows a .pdb file as "unversioned" which is true, but it should have been ignored. Weirder still, it shows with a minus-sign icon in explorer. I attached screenshots. What should I do to get it to really ignore the .pdb files?


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].

screenshot1.jpg screenshot2.jpg
Received on 2011-11-08 22:28:16 CET

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

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