On Thu, Jul 21, 2011 at 00:36, Andy Canfield <andy.canfield_at_pimco.mobi> wrote:
>>> Alternatively, the SVN protocol will go to the svnserve program.
>>> Below the mod_dav_syn layer and the svnserve layer and the repository
>>> layer is the "Subversion Repository". Significantly, this is diagrammed
>>> data, not code. So mod_dav_syn must contain the code to manipulate the
>>> repository, and svnserve must also contain the code to manipulate the
>>> repository, and the Client Library (because of Local access) must contain
>>> the code to manipulate the repository.
>>> Below the "Subversion Repository" component is either "Berkeley DB" or
>>> "FSFS". I have already decided to use "FSFS" since I can look at it as
>>> sitting on the disk and therefore it is more conceptually transparent.
>> FSFS doesn't expose the files directly. It's still a database of
>> sorts, just not a BDB database. You still need a Subversion client to
>> access the files.
> But I don't need a Subversion client to see the files, to read the files,
> and therefore to learn how things are stored. I'm the kind of guy who has
> looked at the directory & file structure created by MySQL for it's
> databases. It becomes possible to see the low-level implementation in case
> that answers a question about the high-level interface. Hey, that's why I
> use Linux and not the Microsoft Black Box System.
You can see the files that FSFS uses to *store* the data in your
repository, but you cannot read the actual contents. IOW, you can put
README.TXT into the repository, but you cannot read the contents of it
by looking at the FSFS data in vi.
>> The concepts described in the book change much less frequently than
>> the code. A significant portion of the "nightly" book applies to older
>> versions - but of course there are changes to cover new/modified
>> functionality, and general edits& reorganization. There was no final
>> version of the book for 1.6.
> I suggest that the "Nightly Build" version be relabelled "Current", and put
Except that it's not necessarily. There may be things in the "Nightly"
book which address a yet-to-be-released version of Subversion, and the
book isn't finalized - there's potentially a new version every day.
But discussion about how the book is managed is off topic for this
mailing list. The book has its own mailing list, issue tracker and
repository. See the "Feedback/Contributing" section on the front page,
Received on 2011-07-21 13:02:22 CEST