Explain the point.

diff --git a/README b/README
index 47e13d88597f6cf28662b31acd1389bb87ae43eb..7665d8509025636c6078ba35cae8c18185c1da37 100644 (file)
--- a/README
+++ b/README
@@ -2,6 +2,10 @@
 
 rcs-fast-import unpacks a git fast-import stream into an RCS file tree
 
+I wrote this as a prod at more recent and putatively more advanced
+version-control systems that don't have .fi importers yet.  If crufty
+old RCS can import these streams, why can't yours?
+
 The metadata in modern DVCSes can't really be stuffed back into RCS,
 but this tool makes a valiant effort and may occasionally be useful
 for extracting the revision histories of individual files from a
@@ -9,4 +13,5 @@ project history.
 
 It keeps the revision structure, comments, authorship dates, and tag names.
 It loses tag dates and comments and authorship information; commits are
-recorded as though they were from the user invoking it.
+recorded as though they were from the user invoking it.  However, all
+import-stream metadata is preserved in RFC-822-style headers in commits.

diff --git a/control b/control
index a3ebf9163972713e7f515160579ccfd7cce94823..f1e3ad960cf8030aa51a9eeaeee7381dad4ea4c2 100644 (file)
--- a/control
+++ b/control
@@ -1,13 +1,17 @@
 # This is not a real Debian control file
 # It's project metadata for the shipper tool
 
-Package: rcs-fast-export
+Package: rcs-fast-import
 
 Description: unpack a git fast-import stream into an RCS file tree
  The metadata in modern DVCSes can't really be stuffed back into RCS,
  but this tool makes a valiant effort and may be useful for extracting
  the revision histories of individual files from a project history.
+.
+ I wrote this as a prod at more recent and putatively more advanced
+ version-control systems that don't have .fi importers yet.  If crufty
+ old RCS can import these streams, why can't yours?
 
-Homepage: http://www.catb.org/~esr/rcs-fast-export
+Homepage: http://www.catb.org/~esr/rcs-fast-import
 
 XBS-Project-Tag-List: version control, git