Differences From:

File ci_fossil.txt part of check-in [10062df2fa] - Reworked my notes regarding 'reconstruct' based on my reading of content.c, checkin.c, and manifest.c by aku on 2007-08-28 05:01:23. [view]

To:

File ci_fossil.txt part of check-in [9d704470c3] - added specification, subsystems to ticket choices, zorro-ed a spelling error by kejoki on 2008-12-13 13:40:44. [view]

@@ -36,14 +36,14 @@
 lot of temporary space in the filesystem to hold all unique revisions
 of all files in their expanded form.
 
 It might be worthwhile to consider an extension of 'reconstruct' which
-is able to incrementally add a set of files to an exiting fossil
+is able to incrementally add a set of files to an existing fossil
 repository already containing revisions. In that case the import tool
 can be changed to incrementally generate the collection for a
 particular revision, import it, and iterate over all revisions in the
 origin repository. This is of course also dependent on the origin
-repository itself, how good it supports such incremental export.
+repository itself, how well it supports such incremental export.
 
 This also leads to a possible method for performing the import using
 only existing functionality ('reconstruct' has not been implemented
 yet). Instead generating an unordered collection for each revision