> The main benefit you get from Subversion's move support
> is that the history is maintained.
While that may be the "main" benefit,
other use cases emphasize
the collaboration aspect of svn,
and have much less use for the history.
Let's say "svn move" always deleted the history.
During reorganization of some projects, that
could actually provide an advantage.
Certainly we derive a large benefit
from "svn move" of large directory trees
(over cvs) regardless of whether the
history gets preserved, because cvs
required each directory to be
"cvs add"ed individually. (Assuming
you meet the requirements for an
"svn move" to work.)
When I go in to fix a broken project,
"svn copy" and "svn move" serve
very useful purposes. A "remove history"
button would also be useful at that point.
Almost all "copies" and "moves"
involve points in the development
where you would like to start a
brand new history.
Another point is licensing. At the
place where you change licensing,
say, at the point where you
transfer a portion of the technology
to Open Source, LGPL, Jakarta,
Sun Community, etc., the history
could generate future misunderstandings
that we can only avoid by deleting
that history at that point.
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 21 18:15:33 2006