You know what they say, "no good deed goes unpunished." Now that we
have changelists (even before The World has them!), I'm finding them
too useful to allow to remain in such a rudimentary state. We
already caught the "directories in changelists" ambiguity and the
"moving files among changelists deserves a shout-out," but that may
be a Really Big Undertaking to iron out. Here are some things that
look smaller, but useful. We IRCed about them a bit, but I'm reading
them into the record, and interested in comments from others:

--no-changelist: an option that can be used anywhere a changelist can
be used, which means "all the modified things that aren't in a
changelist." An obvious use: "svn changelist --no-changelist
newchangelistname" to mark all your currently unchangelisted changes,
say before working on an interrupt or distraction. With the new
flagging of move-among-changelists feature, this gives you some help
in avoiding overlapping changelists. I haven't thought through what
this means for all cangelist-aware commands, there might be some
surprises there, somewhere.

svn changelist --work-on changelistname (or some such syntax):
meaning "any modification I make from now on should automatically be
added to changelistname." This automatic change collection is quite
similar to an extremely popular ClearCase feature (which ClearCase
officially calls "mkbranch," but which you can think of as
"automatic, or latent, branch creation"). Again, the warning about
changing change lists in mid stream interacts pleasantly. This might
be easier to do after the admin directory is centralized, should that
happen.