On Mon, 13 Apr 2009 21:44:32 -0400, Lew wrote:
It suffices simply to distribute the latest version. Incorporating the
entire history of an artifact in the artifact does little to aid anyone,
in the common case. To protect in the uncommon case, one could include
a version-history report as a separate document, generated by the VC
system.
That only works if the VCS can maintain history at the module or project
level, rather than the individual file level. The last vcs I used that
could do that was ICL's Advanced Data Dictionary System, but that's long
extinct - AFAIK it died with VME/B.
I'm know I'm out of touch here: I currently just use cvs. It has no
concept of anything wider than individual file-level version control[1],
but can svn and git do any better?
[1] Yes, I know that it can commit a bunch of files, applying the same
comment to all of them, but the file version numbers aren't synchronized.
history. It's the wrongness of file history in the file that is the problem