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

TSVN 1.8.x prefers svn:global-ignores

From: BIRD Neil <Neil.BIRD_at_uk.thalesgroup.com>
Date: Tue, 15 Oct 2013 15:04:55 +0100

It seems as if TSVN 1.8.x is preferring to set svn:global-ignores on directories instead of svn:ignore.

  If I have two files in a directory to ignore, select them in an explorer window, I can choose to ignore them by name, and they end up in svn:ignore. They then also trigger the “remove from ignore list” option.

  However, if I try to do it from “check for modifications” or the commit dialogue, which is the most common way I find files that need ignoring, they *always* get added to a local svn:global-ignores. I don't choose a recursive option but they would then still be ignored recursively, and also they then don't get the “remove from ignore list” option. On top of that, we still have mostly SVN 1.7 users at the moment and so the ignore won't work anyway.

  Is this intended behaviour? Am I doing something wrong? Is there a way to work around it?

  Since svn:global-ignores is part of the new server-side config set-up, I wouldn't really expect it to be changed on a per-file bases like the use cases above (like you wouldn't change auto-props very often), so I'm at a bit of a loss to understand why it's going for it. I can only see that it would be preferred over actually recursively setting svn:ignore when that was required, but TBH I don't see that being a very common occurance. That may be just the way I use it.

[neil_at_fnx ~]# rm -f .signature
[neil_at_fnx ~]# ls -l .signature
ls: .signature: No such file or directory
[neil_at_fnx ~]# exit
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-10-15 16:05:06 CEST

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.