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

RE: Feature Proposal: Local Ignores

From: Bolstridge, Andrew <andy.bolstridge_at_intergraph.com>
Date: Tue, 10 Feb 2009 10:00:49 -0000

˜ "I assume by asking for "local" ignores you want something like global-ignores"


Or he's just confused by the terminology - 'global' ignores that turn out to only apply to your local workstation.


Personally, I think it makes perfect sense to store this info in the repository, this isn't a distributed SCM, everyone who connects expects to be working together, so having the option to (truly) globally ignore build objects is a sensible one. It would make administering SVN easier in a corporate environment.

The flaw in the argument below is that only 1 person needs a set of ignores for his IDE, but forgets that if another person starts to use the same IDE, you have to copy the ignore-list to his workstation too (making sure you don't forget!) or your repo suddenly starts to get filled with very large, useless objects.


Just my tuppence.



From: Bob Archer [mailto:bob.archer_at_amsi.com]
Sent: Monday, February 09, 2009 3:54 PM
To: Markus KARG; users_at_subversion.tigris.org
Subject: RE: Feature Proposal: Local Ignores


I assume you know that global-ignores are a client side configuration. These can be used by each user to set up ignore patters for their machine. So, you may use Emacs and want to ignore stuff that it creates while I use Studio and want to ignore its artifacts?


I assume by asking for "local" ignores you want something like global-ignores but have it only apply to a specific working copy? I'm not sure what advantage this has? Also, it would be quite a pain to admin it. You can to be copying some ignore file to each WC. Or, you have to add a path specific ignore to some local config file?



Example: Some users will use Eclipse, others will use NetBeans, and so on. These IDEs store additional information in the SVN working copy, and to prevent SVN from treating them as modifications, currently all these artefacts have to be masked by svn:ignore. So time after time, svn:ignore collects more and more of these things. Each new IDE leads to more svn:ignores -- even when only one programmer in the team is using this particular tool.


It makes no sense to store this information in the repository, since it is not dependent of the project, but dependent of the programmer or his machine. So it would make sense to have "local ignores": Things that will be ignored by the local SVN client, but are not stored in the SVN repository but solely (a) in the machine's configuration, (b) in the user's profile, (c) in the local workspace.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-10 15:36:14 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.