Blair Zajac <blair@orcaware.com> writes:
> I noticed that the book has inconsistent command line option spacing
> with a space or no space after the -r option:
>
> % cd svn/doc/book/book
> grep ' -r' *
> ch03.xml:$svn log -r {11/20/02}:4040
> ch03.xml:$ svn log -r 19:5 # shows logs 5 through 19 in reverse or
> der
> ch03.xml:$ svn log -r 8 # shows log for revision 8
> ch03.xml:$ svn log -r 8 -v
> ch03.xml:$ svn log -r 2
> ch04.xml:$ svn diff -r343:344 http://svn.example.com/repos/trunk/calc
> ch04.xml:$ svn merge -r343:344 http://svn.example.com/repos/trunk/calc
> ch04.xml:$ svn diff -r343:344 http://svn.example.com/repos/trunk/calc > patch
> file
> ch04.xml:$ svn merge -r343:344 http://svn.example.com/repos/trunk/calc my-cal
> c-branch
> ch04.xml:$ svn merge -r 303:302 http://svn.example.com/trunk/calc
> .
> .
> .
>
> Subversion handles both just fine, but should we refer to one usage
> over the other? I'm not a fan of the -rXXX:YYY and visually prefer
> to see the whitespace in there.
I agree. Ben? Mike? If we have a consensus, let's just make sure we
put it in doc/book/HACKING.
Oh, and what did we decide WRT shortopts usages vs longopts usage in
the book?
-Fitz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 10 15:41:59 2002