Overview
SHA1 Hash: | ece2c766a26a7081eadcccf8492daaa8f91096b6 |
---|---|
Date: | 2009-04-11 12:53:00 |
User: | drh |
Comment: | Merge in wiki typo fixes. |
Timelines: | ancestors | descendants | both | trunk |
Other Links: | files | ZIP archive | manifest |
Tags And Properties
- branch=trunk inherited from [a28c83647d]
- sym-trunk inherited from [a28c83647d]
Changes
[hide diffs]Modified www/fileformat.wiki from [e6fabaf4cd] to [9924363ba6].
@@ -139,11 +139,11 @@ </blockquote> <p> A manifest has zero or more F-cards. Each F-card defines a file (other than the manifest itself) which is part of the check-in that -the manifest defines. There are two, three, or three arguments. +the manifest defines. There are two, three, or four arguments. The first argument is the pathname of the file in the check-in relative to the root of the project file hierarchy. No ".." or "." directories are allowed within the filename. Space characters are escaped as in C-card comment text. Backslash characters and newlines are not allowed @@ -294,11 +294,11 @@ <b>Z</b> <i>checksum</i><br /> </blockquote> <p> A control artifact must have one D card and one Z card and -one or more or more T cards. No other cards or other text is +one or more T cards. No other cards or other text is allowed in a control artifact. Control artifacts might be PGP clearsigned.</p> <p>The D card and the Z card of a control artifact are the same as in a manifest.</p>