Yeah, good points.
Hmmm. I dunno. Personally, I think I'm gonna punt on this one for
now, as there are more pressing matters before us anyway. Maybe
someone will think of an elegant solution, though.
-K
Nicholas Riley <njriley@uiuc.edu> writes:
> - It blurs the distinction between options and commands to an extent
> that I think will ultimately be confusing. It's great that svn
> doesn't have the stupid 'do I put it before or after the command?'
> distinction that cvs uses. Someone seeing, for example, 'svn -R -x'
> in a shell script will become confused. Would you allow 'svn -Rx' for
> that matter?
>
> - It's non-extensible. It is just a matter of time before people will
> ask for this kind of shorthand to apply to lots of file metadata that
> is ultimately mapped to properties in the repository - permissions,
> attributes, file flags, etc. It'd make sense for each of these to
> emulate the corresponding commands - svn chmod, svn chattr, svn
> chflags, etc., so why not do it that way from the start?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 6 21:02:16 2002