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

Re: (FS) operational question

From: Karl Fogel <kfogel_at_galois.collab.net>
Date: 2001-01-02 03:08:24 CET

Greg Stein <gstein@lyra.org> writes:
> > But the client-state report is not driven by the version URL; it's
> > driven by the version numbers in the wc's entries files.
> Agreed. And when fragmentation occurs, this report is larger.

But fragmentation of the versions in the entries files won't occur
(beyond what's strictly necessary), because the version numbers of
unchanged entities can be updated along with the changed ones.

To do this, svn_wc_get_update_editor() needs to take revision arg and
a target arguments arg, so it can know what entities were "included"
in the update. It already takes the former, and can easily take the

> If the revision number is to be updated for an entry, then we must also
> update the version resource URL. If not... We In Big Heap-um Trouble.
> Therefore, we must respond with all of the new version resource URLs when an
> update occurs.

We're already in trouble, because we're recording the same information
twice: the revision number in the entries file is apparently not
sufficient, so we're recording it in a version resource URL too??

This is what "network layer implementation creeping into working copy
library" means. :-)
Received on Sat Oct 21 14:36:19 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.