Differences From:
File www/pop.html part of check-in [469002ccdf] - Added navbar to all pages, linking back to the index. Fixed typo in the index page. by aku on 2007-09-12 04:19:59. Also file www/pop.html part of check-in [bbcb6326c9] - Pulled in the navbar and timeline changes. by aku on 2007-09-17 00:58:51. [view]
To:
File www/pop.html part of check-in [852dbbb65d] - Update homepage with links to competing projects. by drh on 2008-02-13 12:39:19. Also file www/pop.html part of check-in [588bb7cd73] - Merged to ed26056bb5. by aku on 2008-02-24 18:50:35. [view]
@@ -13,10 +13,11 @@ </p> <ul> <li><p>A project consists of source files, wiki pages, and -trouble tickets. All historical copies of all these -entities are saved. The project maintains an audit +trouble tickets, and control files (collectively "artifacts"). +All historical copies of all artifacts +are saved. The project maintains an audit trail.</p></li> <li><p>A project resides in one or more repositories. Each repository is administered and operates independently @@ -31,47 +32,47 @@ The local state identifies the authorized users and access policies for a particular repository.</p></li> <li><p>The global state of a repository is an unordered -collection of files. Each file is named by -its SHA1 hash encoded in hexadecimal. +collection of artifacts. Each artifact is named by +its SHA1 hash encoded in lowercase hexadecimal. In many contexts, the name can be abbreviated to a unique prefix. A five- or six-character prefix usually suffices to uniquely identify a file.</p></li> -<li><p>Because files are named by their SHA1 hash, all files -are immutable. Any change to the content of a file also -changes the hash that forms the files name, thus -creating a new file. Both the old original version of the -file and the new change are preserved under different names.</p></li> +<li><p>Because artifacts are named by their SHA1 hash, all artifacts +are immutable. Any change to the content of a artifact also +changes the hash that forms the artifacts name, thus +creating a new artifact. Both the old original version of the +artifact and the new change are preserved under different names.</p></li> -<li><p>It is theoretically possible for two files with different +<li><p>It is theoretically possible for two artifacts with different content to share the same hash. But finding two such -files is so incredibly difficult and unlikely that we +artifacts is so incredibly difficult and unlikely that we consider it to be an impossibility.</p></li> -<li><p>The signature of a file is the SHA1 hash of the -file itself, exactly as it appears on disk. No prefix -or meta-information about the file is added before computing +<li><p>The signature of an artifact is the SHA1 hash of the +artifact itself, exactly as it would appear in a disk file. No prefix +or meta-information about the artifact is added before computing the hash. So you can always find the SHA1 signature of a file by using the "sha1sum" command-line utility.</p></li> -<li><p>The files that comprise the global state of a repository +<li><p>The artifacts that comprise the global state of a repository are the complete global state of that repository. The SQLite database that holds the repository contains additional information -about linkages between files, but all of that added information +about linkages between artifacts, but all of that added information can be discarded and reconstructed by rescanning the content -files.</p></li> +artifacts.</p></li> <li><p>Two repositories for the same project can synchronize -their global states simply by sharing files. The local +their global states simply by sharing artifacts. The local state of repositories is not normally synchronized or shared.</p></li> -<li><p>Every repository has a special file at the top-level +<li><p>Every baseline has a special file at the top-level named "manifest" which is an index of all other files in -the system. The manifest is automatically created and +that baseline. The manifest is automatically created and maintained by the system.</p></li> <li><p>The <a href="fileformat.html">file formats</a> used by Fossil are all very simple so that with access