I actually avoid using "ci" because it doesn't convey the
same connotations as "commit". I tell people to "co" all the
time, since it's a common abbreviation for "checkout", and that's
what it does. "st" is not a common abbreviation for "status", and
if I were a new user to svn, I'd wonder about it if I saw it in,
say, a script, and it's the sort of command that would find its
way into a script, if that's what people are used to typing at
the command line, it's what they'll put in a script.
-Peter
> -----Original Message-----
> From: Ben Collins-Sussman [mailto:sussman@collab.net]
> Sent: Monday, May 21, 2001 1:56 PM
> To: Peter Vogel
> Cc: Greg Stein; dev@subversion.tigris.org
> Subject: Re: ugly aliases
>
>
> Peter Vogel <pvogel@arsin.com> writes:
>
> > Would "stat" be an acceptable alternative? Not that I have
> > voting rights or anything, but I really *hate* aliases that
> > don't communicate what they really are. When I read Greg's
> > list, I had no idea what pl,pg,ps,st,df and di did. I
> > would know what svn stat did :-) And as a CM admin, when I
> > tell a user "run svn stat" it flows nicely off the tongue, but
> > if I say "run svn ess-tee" it doesn't and it doesn't tell them
> > what it's really gonna do. Is two keystrokes that much to pay
> > for clarity?
>
> It's not an issue of mutual exclusivity. I say keep 'st' and 'stat'
> both!
>
> But while I'm reading your logic: are you wary of telling your users
> to 'co' and 'ci' as well? Those are pretty common CVS abbreviations,
> and there's no way to tell what they mean either. :)
>
> Bikeshed,
>
> Ben
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:30 2006