Hi Bjoern, > I just tried to add an svn:ignored dir. That works.
Sure - svn:ignore is just for ignoring the item in status and recursive commits. > If someone does a "svn diff" in a module, and sees: > ? source/somenewfile.cxx > ? source/somenewfile.hxx > he might be tempted to do a 'svn add *; svn ci -m "my message"' > and goes to grap a coffee. When he returns he has happily commited the > output trees. That seems kinda dangerous to me. Well, admittedly the intention for my svn:ignore request was never to prevent people from committing them. As I wrote in my original mail, it's about the noise produced by "svn status" which bothers me. (For instance because I usually check my CWS for uncommitted files before passing it to QA or finally deleting it). If somebody really commits an output tree, we can still a) shot her and b) do an "svn delete" (which nowadays is much easier than fixing the same problem in CVS would have been.). > If we svn:ignore output trees, we should also prevent them from being > commited (if we have a list of platforms that are svn:ignored, we could > also specifically look for those in the precommit hook). I am undecided here. If you wish - do it. It might be harder to achieve, as it requires people to update the script when new platforms are born, and in opposite to updating svn:ignore, that's nothing an ordinary developer can do. > BTW this is just as dangerous when having the output trees in global > ignore in the config. I never claimed to invent the idiot-proof solution :) Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
