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

Re: UI interpretation quetsions: --changelist + --depth

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: Sat, 26 Jan 2008 18:25:13 -0600

I do think Julian has at least one valid point: people familiar with
perforce are going to find svn's definition of changelist a bit odd.
In perforce, '--changelist foo' is a specific list of paths. It
doesn't matter where you're sitting in the working copy; it's always
the same complete list of paths. It really does mean "act on this
specific list of targets", rather than "do some recursion on some
target and filter whatever you find".

Of course, the reason the perforce implementation is even possible is
because the server is tracking every working copy and every file
'opened' for editing. The list of changed paths is produced instantly
(i.e. no wc tree-walking) by consulting a server database.

So while I *like* this interpretation, there's no way svn can ever get
there unless we teach libsvn_wc to manage a central database of
changelists in ~/.subversion/. Given our current libsvn_wc design,
Mike's implementation of 'make it a filter' is the only reasonable
consistent behavior, I think.

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-01-27 01:25:25 CET

This is an archived mail posted to the Subversion Dev mailing list.