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

Enhancement: displaced .svn

From: Vladimír Marek <vlmarek_at_volny.cz>
Date: 2005-07-20 14:32:22 CEST


I was thinking for some time about new feature, displaced .svn. As I
don't know svn internals, I'm looking at it just as user. Also it might
been asked and answered before, but I haven't found it.

Normally in every directory of working copy you have '.svn' directory
containing some metadata required for svn. I am thinking about way
getting those metadata out of actual working copy. My idea from the user
point of view is to split working copy directory and metadata directory
into two independent paths.

You would have environment variable like SVN_METADATA defining the head.

When the variable would not be set, everything would work as normally.


If you would set SVN_METADATA to /work/project.meta, it would work as:

working copy:


I hope you have the idea.

a) Your working copy would not be clobbered, you could just tar.gz it
  and ship
b) Imagine having network drive used for collaboration. You could have
  the drive under svn control with the metadata stored locally, which
  would not bother other people using that drive. The drive even does
  not 'need to know' that it's versioned. And you would not vaste
  network drive space for your obsession by svn :)
c) You could use b) as poor man's incremental backup, without affecting
  the data

My questions:
Is it sane from the svn internals view ?
Do I have any chance to get it implemented ? :)
If I start to create patch for this, is there chance to get it to the
  trunk ? Under what conditions ?

Thank you


  • application/pgp-signature attachment: stored
Received on Wed Jul 20 23:06:28 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.