Differences From:

File www/fileformat.html part of check-in [b807acf62e] - Documentation updates by drh on 2007-07-24 12:52:32. [view]

To:

File www/fileformat.html part of check-in [01e7596a98] - File format document change: UUIDs use lowercase not uppercase hex. by drh on 2007-07-24 18:15:40. [view]

@@ -108,9 +108,9 @@
 <p>
 A manifest has zero or one P-lines.  Most manifests have one P-line.
 The P-line has a varying number of arguments that
 defines other manifests from which the current manifest
-is derived.  Each argument is an 40-character uppercase
+is derived.  Each argument is an 40-character lowercase
 hexadecimal SHA1 of the predecessor manifest.  All arguments
 to the P-line must be unique to that line.
 The first predecessor is the manifests direct ancestor.
 Other arguments define manifests with which the first was
@@ -122,9 +122,9 @@
 <p>
 A manifest may optionally have a single R-line.  The R-line has
 a single argument which is the MD5 checksum of all files in
 the baseline except the manifest itself.  The checksum is expressed
-as 32-characters of uppercase hexadecimal.   The checksum is
+as 32-characters of lowercase hexadecimal.   The checksum is
 computed as follows:  For each file in the baseline (except for
 the manifest itself) in strict sorted lexigraphical order,
 take the pathname of the file relative to the root of the
 repository, append a single space (ASCII 0x20), the
@@ -141,9 +141,9 @@
 </p>
 
 <p>
 A manifest has an option Z-line as its last line.  The argument
-to the Z-line is a 32-character uppercase hexadecimal MD5 hash
+to the Z-line is a 32-character lowercase hexadecimal MD5 hash
 of all prior lines of the manifest up to and including the newline
 character that immediately preceeds the "Z".  The Z-line is just
 a sanity check to prove that the manifest is well-formed and
 consistent.