On Monday 13 October 2008 Maurice van der Pot wrote:
> On Mon, Oct 13, 2008 at 05:12:21PM +0200, Philipp Marek wrote:
> > > apparently, the "/etc/fsvs/xxxxxxx/Urls" file is modified
> > > *after* the "fsvs commit" command has finished.
> >
> > Yes, this is per design.
>
> Could you elaborate on this?
FSVS cannot store more than a single revision number (per URL) - there are no
mixed working copies (as yet).
When FSVS can store the revision number(s) for each entry separately (as I've
got on my TODO), it might be possible to drop that; but I'm not yet sure.
Part of the problem is that FSVS has to tell the repository (on update) which
entry is at which revision, so that it can get the changed entries.
If a working copy tree has to be completely traversed, so that FSVS knows what
the base revision is [*] -- and that for each URL you want to update! -- it
might be a problem.
* Simply giving the repository a list of (entry, rev#) doesn't work really -
for 200k entries the list is a bit big, and I think that would affect the
communication negatively.
As long as there's mostly a single revision, perhaps with a few entries
somewhere else, the report is small enough.
> A possible solution for this guy's (and my) problem would be not to
> rewrite Urls for each commit. It hasn't changed after all, so why should
> it be overwritten?
But is has changed ... the WC is at another revision of the URL.
And keeping that out of a commit, eg. by using a separate file in WAA (like
the entry list), doesn't help - we want to know "which mix of URLs at which
revisions was the machine 13 months ago", so that it can be completely
restored.
Regards,
Phil
--
Versioning your /etc, /home or even your whole installation?
Try fsvs (fsvs.tigris.org)!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
