Re: default ignores
From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Tue, 17 Apr 2012 13:34:50 -0500
On Tue, Apr 17, 2012 at 1:08 PM, James French
Sorry, but no. A user can't ever un-add something he has committed to
> Silently failing to add important files I think is worse because you simply don't know that its happened until something goes wrong later.
But you just said the user was supposed to check... It is easy to add
> I still believe that svn is a source control system that each user must take responsibility for and configure how they want.
Of course, but defaults should be there for the common case.
> I don't think that config decisions should be taken by the core product. What if a '.a' file means something else on a different platform? Its the arbitrary nature of the excludes I don't like either (ie primarily supports the svn dev's main platform).
That's why it is in a config file, not hardcoded. Make it do whatever
> One could organise it so the build trees are separate to source trees which completely gets round the problem of accidentally checking in object files... This is what I've got but I'm being penalised because other people mix their build output files in with their source.
There is a worse problem of committing binaries in the mix, especially
-- Les Mikesell lesmikesell_at_gmail.comReceived on 2012-04-17 20:35:22 CEST
This is an archived mail posted to the Subversion Users mailing list.