Re: svn commit: rev 1807 - trunk trunk/subversion/clients/cmdline

> To: dev@subversion.tigris.org
> Cc: svn@subversion.tigris.org
> From: Ben Collins-Sussman <sussman@collab.net>
> Date: 27 Apr 2002 13:41:01 -0500
> Subject: Re: svn commit: rev 1807 - trunk trunk/subversion/clients/cmdline
 
> Also, regarding Greg Hudson's idea about
>
> U foo
> U bar
> # Updated to revision 5
>
> I'm not sure we really need a comment character or anything like
> that. We're certainly not using one when we do a commit:
>
> Sending foo
> Sending bar
> Committed revision 5
>
> If people are worried about scripts being able to parse svn's output,
> then it's just a matter of writing decent regexps.

    It's not scripts *I'm* worried about, it's ad hoc greps. I'm used to
    things like
> cvs up 2>/dev/null|grep -E 'C '

    Sure, the space gets me what I need, but there could be an 'A' flag,
    and a notice beginning with 'A '. Generally speaking, disambiguating
    these two types of output as easily as possible would be nice, and
    won't hurt.
 

-- 
FreeBSD 4.4-STABLE
10:45PM up 12 days, 11:57, 9 users, load averages: 0.17, 0.07, 0.02
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org