On Feb 9, 2009, at 20:56, Tony Butt wrote:
> On Mon, 2009-02-09 at 20:41 -0600, Ryan Schmidt wrote:
>> On Feb 9, 2009, at 18:43, Murli Varadachari wrote:
>>> In my current ~/config file the “global-ignores” property is
>>> commented out [ default installation].
>>> However I noticed that “svn status” on my WC ignores shared
>>> objects “.so” even if the svn:ignore property is *not* set. So
>>> where / how
>>> does the svn client make this determination. Is this the new
>>> default or a bug?
>>> I did not have this problem when using 1.4.x . My current
>>> environment uses 1.5.3 client on a linux platform.
>> This is a feature, not a bug. .so was added to the default global-
>> ignores in Subversion 1.5 via this feature request:
>> If you do not want to ignore .so files, uncomment the global-ignores
>> line in your config file and define it the way you want it.
> Is there a way to find the default global-ignores without trawling
> through the source code?
> I routinely configure the global-ignores in the config file, but would
> like to know what side-effects this is causing (by not ignoring some
> other files)
I think the default global-ignores get written into any new config
files Subversion creates for you. So you could run:
$ svn --config-dir /tmp/svn 2>/dev/null
and then examine the global-ignores line in the file /tmp/svn/config:
$ grep global-ignores /tmp/svn/config
### Set global-ignores to a set of whitespace-delimited globs
# global-ignores = *.o *.lo *.la *.al .libs *.so *.so.[0-9]* *.a
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-10 04:37:16 CET