Garrett Rooney wrote:
>On Fri, Jul 26, 2002 at 04:16:41PM -0700, Blair Zajac wrote:
>
>
>>rooneg@tigris.org wrote:
>>
>>
>>>+@example
>>>+$ svn ls http://svn.collab.net/repos/svn
>>>+http://svn.collab.net/repos/svn:
>>>+_ 2738 bmatzell 0 Jul 26 13:07 clients/
>>>+_ 2743 rooneg 0 Jul 26 18:07 trunk/
>>>+_ 2703 brane 0 Jul 24 22:07 branches/
>>>+P 2734 kfogel 2331 Jul 26 10:07 COMMITTERS
>>>+_ 2698 rooneg 0 Jul 24 18:07 tags/
>>>+@end example
>>>+
>>>+The columns tell you if there file has any properties (``P'' if it does,
>>>+``_'' if it doesn't), the revision it was last updated at, the user who
>>>+last updated it, it's size, the date it was last updated, and the filename.
>>>+
>>>
>>>
>>This is inconsistent with svn status, where it prints ' ' if there
>>are no properities and '_' if there are some. It would be good if
>>the two commands could be consistent.
>>
>>Granted, having printing a space if there's nothing there may
>>be odd, but svn status already does that.
>>
>>
>
>i compare it more to 'svn st -v', which does print the _ if nothing
>has been changed.
>
>actually, now that you mention it, why the hell does status not print
>the _ in the normal case anyway? i always thought that was weird.
>
>
Status only prints the second _ if the file *has* any properties.
--
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 27 03:55:24 2002