View Single Post
Old 16 October 2016, 14:02   #149
Registered User
Join Date: Aug 2007
Location: berlin/germany
Posts: 931
Originally Posted by Olaf Barthel View Post
This is likely to take a lot of work to compensate for the loss of (for lack of a better word) "metadata" which the individual module history tags represent. I expect that this would likely to impact productivity more than the productivity gains attainable from switching to Git could compensate for.

With the tags gone, it becomes difficult to track which release each collection of files corresponds to. And let's not get into the bigger problem of matching those tags against the respective operating system release which they are a part of. There are V36 components in Kickstart 2.04 (V37), 3.0 (V39) and 3.1 (V40), there are V39 components in 3.1, etc. The version numbers of components were usually changed only if the respective code would no longer work with earlier releases, which explains why it looks like patchwork.

The tags are like "thumb tacks" (there's a pun there somewhere, I suppose) which pin down the collection of files that makes up a specific version. It's fundamentally what "software configuration management" tools are supposed to be doing, so it's not an "expendable" property of the subversion repository.
It shouldnt be impossible to import the commit history into a modern source management system. Except it might be more difficult with more orthodox formats. But then, how can you browse comit history stored lile that today?

Ideally sources should be imprted to git or svn as far as possible while keeping the originals for reference.
wawa is offline  
Page generated in 0.03903 seconds with 10 queries