I read the paper on Subversion with great interest as I am looking around for
something to replace the ageing SCCS system we are using now, and I saw many
of the problems in CVS that it identifies.
Although I don't have much time for programming, I would be very interested
in adopting and *testing* SVN. Part of this adoption would be my writing an
SCCS to SVN conversion tool. That's not as straightforward as CVS to SVN as
SCCS is a per-file version system, but I have a few ideas, like considering
all files deltaed within two minutes of one another to be of one revision.
Obviously, SCCS2SVN would be contributed back to the SVN project. It would
be a Unix script, based on SCCS2RCS --- unless it would be better done
otherwise; but as it's converting from SCCS which only exists on Unix, it
doesn't have to be ported to other platforms.
There are some other details about how we use SCCS here and I have a few
wishes for SVN but I'll bore you with all that if you're interested in my
offer.
Any use ?
Michael Mounteney,
Landcroft Computing Ltd.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:42 2006