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

Re: Coping with repository bloat

From: Pete Gonzalez <pgonzalez_at_bluel.com>
Date: 2004-05-14 19:59:54 CEST

At 04:27 AM 5/14/2004, jpsa@jjdash.demon.co.uk wrote:
> > All right, providing *integrated* exclusive access to unversioned files
> > is the best argument to date. Of course, Subversion hasn't a chance of
> > doing this until it supports exclusive locks -- my pet project for 1.1 :-)
>Some of these problems sound as if they would be neatly solved by allowing
>svn:externals to refer to unversioned files?

That's an interesting idea. But it would be nice to have some
version control features such as commits, authorship, deleting
of deadwood, metadata, etc.

I think that probably the most general approach is the suggested
idea for a tool that lets you fold together revision histories
in the database, i.e. "combine all changes between Jun 1, 2003
and Jan 1, 2004 into a single revision." With this feature, you
could just write a check-in hook script that e.g. automatically
deletes everything before the most recent 3 revisions for ".bmp"
files (or files with a particular property setting, etc.).

However, I'm guessing that this feature might lead to a lot of
subtle complications for the current update/merging implementation.
But as Subversion's job description is to "manage revisions",
I think this would be a very apropos addition. There is nothing
strange or outlandish about people wanting to manage histories,
and I'm guessing that the reason this has not received more attention
is simply that not many people have gotten to the "big repository"
stage yet.

At the very least, since CVS has this feature ("cvs admin -o"),
Subversion should have it under the principle that Subversion
is a replacement for CVS. :-D


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat May 15 05:26:18 2004

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.