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

RE: Re: [rfc]Checkout without the .svn Directories

From: Robert Hunter <robert.hunter_at_gen-i.co.nz>
Date: 2004-12-09 03:48:47 CET

Rick Johnson wrote:
> For me, having the ability to have an updateable copy (I won't call it a
> working copy since no work would be done in it), that isn't twice the
> size of the exported copy would be great. It would either allow me to
> host twice as many sites on a particular server or halve the amount of
> data I'm backing up each night. Either of these things would lessen my
> administrative load and make me happy.

> I am very happy with Subversion and using 'svn up' to update a website
> is great but the amount of space the working copy takes up vs. the size
> of the site gets me down sometimes.

It's probably been discussed before, but if the text-base copies are
always going to be the same as the "real" files, surely a user
could do without the text-base altogether, and the contents could
be implied by the real files?

I'm thinking two implemenations: one script around the existing Subversion,
and the other being a feature request/patch to the Subversion client.

Hacky Script Checkout:
        Check out project
        Remove all .svn/text-base/

Hacky Script Update:
        Copy (or link) real files to .svn/text-base/${file}.svn-base
        svn update
        Remove all .svn/text-base/

Obviously the script would be an interim solution; the Subversion client
would ideally cope gracefully with a missing text-base on update by
either populating base through the real copies, or simply opening
the real files (instead of the text-base) when merging differences.

This kind behaviour could be implicit or explicit -- I can think of
arguments for either side.

Additionally, there could be an option to not create base copies in the
first place -- something like "svn checkout --no-base-copy".


Robert Hunter
This communication, including any attachments, is confidential.
If you are not the intended recipient, you should not read it
- please contact me immediately, destroy it, and do not copy
or use any part of this communication or disclose anything about it,
Thank you.
Please note that this communication does not designate an information system
for the purposes of the Electronic Transactions Act 2002
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 9 03:51:18 2004

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.