Hallo Al & Co., > half? more like a quarter, but even so, the real history is in > RCS, which doesn't carry over anyway. It has gotten quite messy > over the years. Those are all factors in my thought of wait for > the split, then start clean. > > For the curious ... > http://www.gnucap.org/devel/gnucap-2010-04-09-RCS.tar.gz > This one has a restart at the time of transition from C to C++.
I know that there is no definitive choice made for a new revision control system, but it is possible to move the RCS file history to git. A search gives several methods to move data from RCS to a new revision control, if the old commit history is important... I tried this: http://stackoverflow.com/questions/1619737/migrate-project-from-rcs-to-git and this mentioned Ruby script (see the typical usage, and example below): http://git.oblomov.eu/rcs-fast-export and obtained a revision history for the archive mentioned above. The (essential?) commit messages are missing and some commits contain a list of n's, no clue why those n's are included. Bas Bas -- _______________________________________________ Gnucap-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnucap-devel
