On 5/9/07, Karl Fogel <kfogel@red-bean.com> wrote:
> I'm not sure how to justify my feeling, beyond just stating it :-).
> We're operating on very little data here: we don't know how often
> users of the command line client will use '--changelist'. I'd rather
> wait until it's been out in the wild for longer, and see what kind of
> feedback we get, rather than snatch option namespace in anticipation
> of complaints that may turn out to be rare.
You might be right, not sure. But I also feel like we're able to make
a better guess this time than in our usual "let's just wait and see if
there's a need".
With a feature like 'svn log --limit', we're not entirely sure how
often users use the --limit switch, and whether it 's worth shortening
it.
With changelists, you either use them or you don't. That is, either
you're working with simple targets / whole tree, or you want to
operate on specific named subsets of the tree. If you define a
changelist, then you're going to use --changelist with *every
subsequent command*. It's the only way to operate on these subsets.
So it feels sort of contradictory to say "hey, define a changelist to
conveniently work against a subset of your tree", but then turn around
and say, "oh, did we we say 'convenient'? I'm sorry, you're going to
have to type --changelist on everything you do."
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 10 03:52:46 2007