On 5/9/07, Julien Cugnière <julien.cugniere@gmail.com> wrote:
> Some external point of view on the changelist naming, in case anyone cares :-)
>
> 2007/5/9, C. Michael Pilato <cmpilato@collab.net>:
> > Ben Collins-Sussman wrote:
> > > I'm hesitant to grab -C. I can't imagine explaining to a user, "yeah,
> > > -c stands for 'change', and -C stands for 'changelist'." Eek.
> >
> > Honestly, my first choice for a shortopt was -L, but I figured folks would
> > freak out about it. To me the key portion of the word "changelist" is "list".
>
> Indeed, it seems to me that what is implemented isn't the notion of a
> "list of changes" (which reminds more of a revision), but rather that
> of a "list of files".
Huh? What's the difference? A directory is certainly includeable in
the list, not just files.
Subversion, historically, has always represented 'changes' as a list
of paths with some sort of action associated with each path. (Add,
delete, modify, etc.) Just run 'svn log -rN -v' and witness the
'changelist' of paths printed out for the revision. This is a
consistent idea.
> Alternatively, it strikes me that the "--changelist" option
> essentially does the same thing as the "--targets" option some of the
> subversion commands take. Would it then make sense to use the same
> options for both ? Subversion would look for a file, and if none is
> found, it would look for a changelist (or filelist, or whatever!). The
> options could then be something like "--targets" and "-T" or "-t".
Actually, --targets and --changelist aren't mutually exclusive; they
can be used together to build a list of targets. So we shouldn't be
turning them into mutually exclusive things.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 9 20:18:50 2007