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

Re: Unversioned files held by repo

From: Jared Hardy <jaredhardy_at_gmail.com>
Date: Wed, 12 Mar 2008 21:17:53 -0700

+1 to the file "history depth = 1" feature, from this user. Good way
of simplifying the issue Mad Scientist! Being forced to keep the same
exact history properties on everything (i.e. history depth is always
infinity) is really annoying.

In case everyone else hasn't noticed, Perforce recently added a
history depth setting to their SCM, where you can define the maximum
history depth you want to keep around for any given file, or general
file type (i.e. mp4). This is really useful for keeping shallow
history of big files, compressed files, and/or even compiled files.
Some use cases might also find it is a better way to track externals,
in an atomic fashion. It allows the user/admin to keep better control
of their repository size, makes obliterate implementation trivial, and
allows *atomic tracking of all files*, not just "source" files.

It seems that at least one SCM has figured out that "designed not to
lose history" might be better extended to "designed not to lose
history, unless the user definitely WANTS it to". It sounds like
Mercurial is also working on overlay and history hole-punching
features, that accomplish the same goals. Isn't an obliterate command
also on SVN's roadmap? What about "selectively obliterate history"?
I've seen a lot of requests for this kind of feature -- stop giving
Mad Scientist such a hard time about it.

:) Jred

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-13 05:18:13 CET

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.