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

Re: Subversion vs. filesystems

From: Kevin Pilch-Bisson <kevin_at_pilch-bisson.net>
Date: 2001-02-01 23:36:48 CET

On Thu, Feb 01, 2001 at 04:28:33PM -0500, Jim Blandy wrote:
> Kevin, you're the fellow who was talking about implementing a genuine
> mountable filesystem that tracked versions, right? What I think would
> be really useful along those lines would be to implement a filesystem
> on top of the *client* library --- you'd get a working directory where
> ordinary "rm", "mv", and "cp" would maintain the meta-information
> Subversion needs to do commits and updates. You could just use Emacs
> dired to mess around in your working copy, and it'd all Just Work.

That is indeed an interesting idea. An immediate problem is how are
files added to the repository automatically, or with a command. If
automatically, then it would need a good way to know what not to include
automatically. If with a command then there can still be the problem of
forgetting to add things.
> Detecting copies is a bit of a challenge, but I think GNU cp is a
> "memory mapped" cp: it maps the entire input file into memory, and
> then does a single write request to create the new file. This means
> that the write uses the exact same pages as the read. Perhaps the
> filesystem could notice which file the pages were coming from,
> recognize that a copy was in progress, and adjust the Subversion
> metainformation appropriately.

I think I am still some time away from actually starting to implement
something, but thanks for the technical help. I'm sure it will come in

Kevin Pilch-Bisson
PGP Public Key At http://pgp.pilch-bisson.net

  • application/pgp-signature attachment: stored
Received on Sat Oct 21 14:36:21 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.