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

Obliterate or exclude folders from version control

From: Mariska Hoogenboom <mariska.hoogenboom_at_gmail.com>
Date: Thu, 10 Dec 2009 05:50:35 -0800 (PST)

Hi all,

First of all, I agree that svn should have an obliterate functionality.

In addition to that, I wonder if anyone else but me would like the possibility of excluding folders or files in an svn repository from version control.

Each commit on a file with this special property would replace the existing entry in the repository instead of adding a delta, but the repository does get a new revision number, so clients know when their working copy is outdated.

This would allow you to use a subversion repository both for source/documentation control and for storing for example big binary build results, without the need to obliterate older versions.

For relatively small projects, the environment can be much simpler: just one svn repository and no need for other repositories/fileshares/workspaces/etc for storing your builds or other binary data for reuse.
Another advantage is the sources and builds are accessible by the same svn client.

And you would have the possibility to store project data that does not need version control (project photo's, mailbox, etc).

What do you think of it?

BR,
Mariska.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2429192

Please start new threads on the <dev_at_subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <dev-subscribe_at_subversion.apache.org>.
Received on 2009-12-10 14:53:10 CET

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.