Re: cvs log -r branch

[Kaz Kylheku]

lawrence.jones@eds.com (Larry Jones) wrote in message 
news:<mailman.2317.1046101377.21513.bug-cvs@gnu.org>...
> Paul Edwards writes:
> > 
> > Is it deliberate behaviour that you have to go
> > 
> > cvs log -rbranch file.c
> > 
> > rather than
> > 
> > cvs log -r branch file.c
> 
> Yes.  See the description of the -r flag in:
> 
>       <http://www.cvshome.org/docs/manual/cvs_16.html#SEC143>

Argh! Thanks guys for giving me a bug to fix in Meta-CVS. :)

When this software generates a CVS command line and passes down
arguments, the option arguments are represented as separate command
arguments.

$ mcvs --debug -nfz3 up | grep cvs
* invoking ("cvs" "-n" "-f" "-z" "3" "up") in directory
"/home/kaz/mcvs/MCVS"
cvs update: Updating .

So now am I going to need a special case hack for options that do not
allow whitespace? Or can I get away with the assumption that an a
one-letter option that has one argument can always be generated as a
single command line parameter with no whitespace between the option
letter and the argument characters?