[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: What should `svn commit' print?

From: Greg Stein <gstein_at_lyra.org>
Date: 2001-01-04 12:21:04 CET

On Wed, Jan 03, 2001 at 11:51:30PM -0600, Ben Collins-Sussman wrote:
> 2. M <- foo.c
> D <- bar.c
> A <- baz.h
> Commit succeeded, repository revision 320.
> [side question: maybe this means that during a checkout or
> update, we'd see the arrow going in the other direction? :) ]

I don't think that the arrows add much. I read it as "foo.c is going to M".
Or possibly assignment: "M takes foo.c".

My second concern (although slight) is the use of shell metacharacters. I
dunno in what cases it will create a hassle, but certain types of parsing
might get tripped up with needing to escape the '<-' pattern.

Personally, I'm not bothered by the full words. Why the need to be terse?
We're down to a single line, which is the important part. No need to be
horizontally-terse :-) Single letters vs words are the same complexity to
parse, yet the word is easier for the human.


Greg Stein, http://www.lyra.org/
Received on Sat Oct 21 14:36:19 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.