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

Making -l a shortcut for --limit (again)

From: David Glasser <glasser_at_mit.edu>
Date: 2007-07-23 18:15:58 CEST

Wee, bikeshed time!

Every so often it is proposed that we make '-l' a shortcut for
'--limit', specifically for 'svn log'. Here's the last time it came
up:

http://svn.haxx.se/dev/archive-2007-03/0476.shtml

I don't think that discussion really got resolved. (Karl suggested
polling users@; not sure if that ever happened.) My (biased)
impression is that there are a fair number of developers who are in
support of this, and another number who are opposed (mostly because of
the "it's only one subcommand" factor).

The main argument for: "I always use --limit (except when using -r)".
Supporting evidence: svk (which has a very similar command-line to
svn) has had -l for years, and svk users (such as myself) seem to find
this a big convenience. It's also worth noting that --limit is the
only command-line argument that we've come up with in the first 7
years of Subversion that begins with L.

I honestly don't understand the counterargument well. "svn log
--limit" is a feature we've had for years, and a non-trivial set of
people say they ~always use it. On the other hand, we're devoting
'-g' in 1.5 to a feature that nobody has used yet (and '-g' isn't even
as mnemonically associated to its expansion as '-l' would be).

I don't want to start a big bikeshed or do anything like call for a
vote, but... I really would like to get more resolution on this than
"a bunch of people want it! a bunch of people don't want it!".

--dave

-- 
David Glasser | glasser_at_mit.edu | http://www.davidglasser.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 23 18:14:54 2007

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.