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

Re: doc/programmer/design/server.texi doesn't know about FSFS

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-05-26 19:04:10 CEST

On May 26, 2005, at 10:55 AM, Andrew Thompson wrote:

> The @node Diffy Storage section(line 647) of server.texi talks
> about rediff'ing previous versions against the newest revision when
> wrapping up a commit.
>
> Would someone like to contribute new text that describes the FSFS
> format, or point me at a nice section of text that can be pasted in?
>
> Text from 1.2.0 release:
>
> Like many other revision control systems, Subversion stores changes as
> differences. It doesn't make complete copies of nodes; instead, it
> stores the @emph{latest} revision as a full text, and previous
> revisions
> as a succession of reverse diffs (the word "diff" is used loosely here
> -- for files, it means vdeltas, for directories, it means a format
> that
> expresses changes to directories).
>
>
> The next section, @node Implementation, mentions only BDB as an
> available filesystem. I believe a one or two line snippet that's
> possibly in the 1.1 release announcement will suffice here.
>
> /me trying to learn the internals...
>
>

I'm not sure it's worth updating the design document. It's five
years old, written before a single line of code was written. The
*principles* are accurate, but I'm not sure it's worth keeping the
details up to date. It's meant to be a 'rough sketch', and is mostly
of archeological interest at this point.

Start by reading svn_fs.h, the public API. Then read libsvn_fs_base/
notes/structure. Then read libsvn_fs_fs/structure.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 26 19:07:32 2005

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