Jul 20, 2005 kl. 2:32 PM skrev Vladimír Marek:
> 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
> 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
> point of view is to split working copy directory and metadata
> into two independent paths.
> You would have environment variable like SVN_METADATA defining the
> 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
> 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 ?
This is A VERY BAD IDEA.
If you're working on more than one project, they will all share
metadata if the environment variable is
"Home is not where you are born, but where your heart finds peace" -
Tommy Nordgren, "The dying old crone"
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Jul 20 23:06:32 2005