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

milestone 1

From: Karl Fogel <kfogel_at_galois.collab.net>
Date: 2000-10-21 06:17:58 CEST

We have our [admittedly self-designated] "Milestone 1" functionality.

Thanks for all for the hard work, everyone!

Want to see it? Go into the subversion/subversion/client dir of a
built tree and run "make check".

The functionality is as described in client/README. Diffidently I
point out that it includes file deletes, as a bonus. Those weren't
actually scheduled for milestone 1, but what the heck, it didn't take
that much extra work... Or rather, I didn't *think* it would take too
much extra work, and then by the time I realized it would, it was too
late to turn back. So they're done now.

There is no network traffic with the filesystem, as you may remember.
The working copy is checked out from a hand-built XML file, commits to
an XML file, and then another working copy updates from that XML file.

The next milestone will hook this all up with the filesystem, over the
network. It would be nice to swap XML deltas with the file system
manually right now, and in fact we could do checkouts that way if we
had data in an fs, but commits wouldn't work with the fs yet.
Filesystem reading functionality is complete (!), but Jim is still
working on writes. There are some subtle things to get right
w.r.t. transactions there, so I don't blame him for not wanting to
rush. (And in fact rather expect the fs to be done long before the
working copy library, at which point we can all fight over who gets
Jim's time.).

Off to bed now, beginning to think we may actually have a useable
program within our lifetimes... :-),
-Karl

P.S. We'll schedule (and more clearly define) the next milestone[s]
next week. Right now, I don't want to think about it.
Received on Sat Oct 21 14:36:12 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.