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

Re: Default value for global-ignores - Import excluded .so files

From: Ryan Schmidt <subversion-2009a_at_ryandesign.com>
Date: Fri, 20 Feb 2009 19:44:07 -0600

On Feb 20, 2009, at 12:29, Justin Johnson wrote:

> On Fri, Feb 20, 2009 at 11:58 AM, JJ <eggsgloriouseggs_at_gmail.com>
> wrote:
>> I currently have the same issue as described in this thread.
>> http://svn.haxx.se/users/archive-2008-11/0211.shtml
>> I'm trying to import the JDK and all .so files are being quietly
>> excluded from the import every time. The above thread points
>> to .so files being included in the default value for global-ignore
>> even though the book doesn't include it in the list, as can be
>> seen at http://svnbook.red-bean.com/nightly/en/
>> svn.advanced.confarea.html#svn.advanced.confarea.opts.
>> My thought is that having default ignore values is a mistake to
>> begin with. It seems dangerous to me to have a default ignore
>> value that prevents Subversion from importing certain files and
>> having that default value quietly documented (ignoring the error
>> in the doc for now) in an obscure section of the documentation or
>> a config file that they wouldn't necessarily read for a long time.
>> Does anyone else agree? Am I missing some important use case that
>> drove this decision in the first place?
> More info. Between 1.4.6 and 1.5.0 .so files were added to the
> default values in http://svn.collab.net/repos/svn/tags/1.5.0/
> subversion/include/svn_config.h.
> Again my point is that I think these default values are dangerous
> and that nothing should be ignored by default.

The fact that .so was added to global-ignores was mentioned on the
list last week:


I suppose the reason why Subversion has certain things in the global-
ignores by default is that it is a best practice to not commit
certain files. For example, some editors will automatically make
backup copies of files you edit, but you would not want to check
those in, because the repository already contains your backups in the
form of previous revisions. It is also a best practice not to commit
files you can recreate from other files that are already in the
repository. So if you have the source code to make a shared library,
then it's recommended not to check in the compiled shared library
itself. Of course you're free to do as you like, and certainly there
are reasons why you would nevertheless like to check in such files.
Subversion does not prevent you from "svn add"-ing such files and
then committing them. Or you can set a different global-ignores
definition that suits your style of work better.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-21 02:45:26 CET

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.