On 4/15/05, Moisei <moisei@gmail.com> wrote:
> Thanks, this url was the reason why I posted my "thoughts".
> Definitely, the specification is the absolutely "must-to-be-done"
> development requirement.
> I just try to help on the "pre-specification" stage where, IMHO,
> use-cases are important step.
> Trying to conclude this long thread, here is my vision of the problem:
>
> On the user side:
> - The feature *is* required by many users, mainly because of the two reasons
> - 1/ disk space usage (that includes the "raw" disk cots, size of
> the repository, etc)
> - 2/ security
> - In both cases, it is talken about user-mistake and not a regular workflow
> - In both cases user interested to eliminate the content of the commited files
> and do not care about directory structure.
i have to admit, if i'd miss something in svn, it is
"obliterate"/"destroy" functionality.
we got around slow working copies and merging/branching problems by
using svk, which works perfect, these guys really did a good job too.
svk uses svn client libs, and stores its data in in the rock-sable svn
datastore .... but it keeps growing ;)
-solo.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 15 10:31:25 2005