Michael Price writes:
> Julian Fitzell writes:
> > > If we are going to use flags, it seems more intuitive to me to always
> > > honor svn:ignore unless some flag (--force?) is used.
> >
> > I have to weigh in strongly in support of this. Presumably you have
> > files being ignored in svn:ignore for a reason. If you really want to
> > override that, you can easily specify --force.
>
> Bah, Humbug. The only thing more annoying would be if '-i' was the
> default action for the 'rm' command. I typed the command line. I
> shouldn't have to "force" anything.
Hm, in this case I'd lean towards requiring the --force option as
well. Look at it this way: whoever runs the repository has decreed a
policy with the svn:ignore prop, you should have to explicitly specify
that you want to override it (in fact, if you were to be completely
consistent, there'd be a "really always ignore these files whatever
option flags are passed" propery, but that's probably going too far).
> > If we don't honour svn:ignore by default, I'm going to spend my time
> > removing generated files that other developers have checked in by
> > mistake even though I set up svn:ignore properly.
>
> Get new developers or make your hiring process more stringent.
ROFL! You think people who administer SCM systems get a say in which
developers get hired? You think developers bother to learn how their
tools work? You think <aagh, must ... stop ... rant ... of ... death>
;-)
--
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 5 22:54:22 2003