--- /dev/null
+ BSD LICENSE
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+
+Redistributions of source code must retain the above copyright
+notice, this list of conditions and the following disclaimer.
+
+Redistributions in binary form must reproduce the above copyright
+notice, this list of conditions and the following disclaimer in the
+documentation and/or other materials provided with the distribution.
+
+Neither name of the this project nor the names of its contributors
+may be used to endorse or promote products derived from this software
+without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR
+CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
+EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
+PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
+PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
+LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
--- /dev/null
+#
+# makefile for sccs2rcs
+#
+VERS=$(shell sed <sccs2rcs -n -e '/version=\(.*\)/s//\1/p')
+
+SOURCES = README COPYING NEWS sccs2rcs sccs2rcs.xml Makefile control
+
+all: sccs2rcs.1
+
+sccs2rcs.1: sccs2rcs.xml
+ xmlto man sccs2rcs.xml
+
+sccs2rcs.html: sccs2rcs.xml
+ xmlto html-nochunks sccs2rcs.xml
+
+clean:
+ rm -f *~ *.1 *.html *.tar.gz MANIFEST SHIPPER.*
+ rm -fr .rs* typescript test/typescript
+
+sccs2rcs-$(VERS).tar.gz: $(SOURCES) sccs2rcs.1
+ @ls $(SOURCES) sccs2rcs.1 | sed s:^:sccs2rcs-$(VERS)/: >MANIFEST
+ @(cd ..; ln -s sccs2rcs sccs2rcs-$(VERS))
+ (cd ..; tar -czvf sccs2rcs/sccs2rcs-$(VERS).tar.gz `cat sccs2rcs/MANIFEST`)
+ @(cd ..; rm sccs2rcs-$(VERS))
+
+version:
+ @echo $(VERS)
+
+dist: sccs2rcs-$(VERS).tar.gz
+
+release: sccs2rcs-$(VERS).tar.gz sccs2rcs.html
+ shipper -u -m -t; make clean
--- /dev/null
+ sccs2rcs project news
+
+1.7: 2010-11-15
+ Added a manual page.
+
+1.6: 2010-10-20
+ Reorganize and expand the header comment so it is actually useful.
+
+1.5: 2007-09-14
+ Bug fix in comment extraction from Peter Grandcourt and Frederic
+ G. Marand.
+
+1.4: 2007-07-13
+ Python rewrite described above. Interface cleanup. Auto-checkout
+ of RCS workfiles corresponding to SCCS workfiles present when started.
+ Lifting of VC mode snapshot info. Initial-comments file.
+
+1.3: 2007-07-10
+ Merges in Brian Berliner's branch hack from the other fork
+ of this script, the one distributed with CVS. That and four SCCS
+ keyword substitutions were the only thing it did that this didn't.
+
+1.2: 2003-04-09
+ Merges in Roger Pilkey's fix for the case in which date spans
+ cross the millenium boundary. Use GNU tac instead of tail, which can't
+ reverse large files properly.
+
+1.1: 2002-08-01
+ I added some portability fixes and the -u option. More importantly,
+ I removed the dependencies on the BSD/SV `sccs' utility; this script
+ will now work on any system that has the base SCCS/RCS tools available.
+
+Descended from, an ancient shellscvript by Ken Cox, with contributions by
+Brian Berliner and others.
+
--- /dev/null
+# This is not a real Debian control file
+# It's project metadata for the shipper tool
+
+Package: sccs2rcs
+
+Description: move an SCCS repository to RCS
+ A tool to convert an existing SCCS history into an RCS history without
+ losing any of the information contained therein. It requires that the
+ SCCS and RCS tools be installed on your system.
+
+Homepage: http://www.catb.org/~esr/sccs2rcs
+
+XBS-Project-Tag-List: SCCS, RCS, version control
#
# 1.6: Reorganize and expand the header comment so it is actually useful.
#
+# 1.7: Added a manual page.
+#
# Eric S. Raymond <esr@thyrsus.com>
import os, sys, getopt, re, commands
+version="1.7"
+
# Here are the translations for SCCS % keywords to RCS-style $ keywords.
# The quotes surround the dollar signs are to fool RCS and later version-
# control systems when the script is checked in. In the unlikely event
--- /dev/null
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE refentry PUBLIC
+ "-//OASIS//DTD DocBook XML V4.1.2//EN"
+ "docbook/docbookx.dtd">
+<refentry id='sccs2rcs.1'>
+<refmeta>
+<refentrytitle>sccs2rcs</refentrytitle>
+<manvolnum>1</manvolnum>
+<refmiscinfo class='date'>Nov 11 2010</refmiscinfo>
+<refmiscinfo class='productname'>sccs2rcs</refmiscinfo>
+<refmiscinfo class='source'>sccs2rcs</refmiscinfo>
+<refmiscinfo class='manual'>Development Tools</refmiscinfo>
+</refmeta>
+<refnamediv id='name'>
+<refname>sccs2rcs</refname>
+<refpurpose>move an SCCS repository to RCS</refpurpose>
+</refnamediv>
+<refsynopsisdiv id='synopsis'>
+
+<cmdsynopsis>
+ <command>sccs2rcs</command>
+ <arg choice='opt'>-c</arg>
+</cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1 id='description'><title>DESCRIPTION</title>
+
+<para><command>sccs2rcs</command> is a script to convert an existing
+SCCS history into an RCS history without losing any of the information
+contained therein. It requires that the SCCS and RCS tools be
+installed on your system. </para>
+
+<para>Run this in a directory with an SCCS subdirectory. It will convert
+all the SCCS files to corresponding RCS master files in a new RCS
+directory; the SCCS data itself is accessed read-only. It will
+complain and terminate if any of the SCCS files are checked out or
+if the RCS directory already exists and is nonempty. If the
+directory contains snapshot auxiliary data produced by Emacs VC mode
+for tagging, that will be used too.</para>
+
+<para>Date, time, author, comments, and branches, are all preserved.
+Most SCCS keywords are translated to RCS keywords; it will
+complain about the exceptions so you can see them.</para>
+
+<para>If this tool fails it will tell you why. `rm -rf RCS; unget SCCS/s.*'
+will recover your initial state.</para>
+
+<para>There is one option. With -c you can specify an initial-comments file.
+Each line should consist of a filename followed by a colon, followed
+by the RCS initial coment to set for that file.</para>
+</refsect1>
+
+<refsect1 id='returns'><title>ERROR RETURNS</title>
+<para>Returns 1 on any error, 0 otherwise.</para>
+</refsect1>
+
+<refsect1 id='author'><title>AUTHOR</title>
+
+<para>Eric S. Raymond <email>esr@thyrsus.com</email>; project page at <ulink
+url='http://www.catb.org/~esr/sccs2rcs'>http://www.catb.org/~esr/sccs2rcs</ulink>.</para>
+</refsect1>
+</refentry>