Marcus Comstedt <marcus@mc.pp.se> writes:
> Ben Collins-Sussman <sussman@collab.net> writes:
>
> > Conceptually, I much prefer the second option. It seems cleaner to
> > me.
> >
> > Up till now, svn commandline switches have always been global; order
> > has never mattered. I would hate to have the placement of --locale
> > change behaviors; I'd like it to be "global" to all target paths on
> > the commandline.
>
> The approach suggested by Ulrich, which is to defer setting the new
> locale until all args have been parsed, also has the feature that
> placement of --locale does not matter. The downside being that you
> can't use --locale to change the interpretation of the command line
> args at all. Exactly what is the intended use of --locale? Can
> anyone produce a reasonable use-case? Discussing the semantics
> without knowing when the option is intended to be used seems rather
> pointless...
Use --locale:
* to specify the charset of the log message being read by -F
* to interpret working copy paths that will be read later on
(i.e. 'svn up', with no args)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 11 23:21:53 2002