By the way, svn 1.5 (not yet released) has a 'changeset' feature built
in. It allows the working copy to track groups of paths with specific
names, and then operate on just those sets of the files (diff, commit,
etc.) It's similar to the perforce changeset feature, except that the
server isn't tracking them -- it's just client-side bookkeeping. It's
nice for managing multple patches in a single working copy.
You might want to take advantage of this in your new emacs code. But
then again, if you're generalizing the changeset management to work
across lots of different VC systems, you've probably already
reinvented this same sort of bookkeeping code in elisp. :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jul 15 18:57:39 2007