Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Link to the manifest documentation from the core concepts. |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
7ff74b20d6620c5464db84745f1e474d |
| User & Date: | andybradford 2014-05-31 15:34:25.728 |
Context
|
2014-05-31
| ||
| 16:37 | Backout [636982a564], which incorrectly calculates aggregate disk checksums when selectively committing files for the initial checkin. check-in: 1a0179abd7 user: joel tags: trunk | |
| 15:34 | Link to the manifest documentation from the core concepts. check-in: 7ff74b20d6 user: andybradford tags: trunk | |
|
2014-05-30
| ||
| 18:12 | integrated wiki-keep-mimetype branch. check-in: 52d242a73b user: stephan tags: trunk | |
Changes
Changes to www/concepts.wiki.
| ︙ | ︙ | |||
122 123 124 125 126 127 128 | order and it can figure out the relationship between those artifacts and reconstruct the complete development history of a software project. <h3>2.2 Manifests</h3> Associated with every check-in is a special file called the | > | | 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 | order and it can figure out the relationship between those artifacts and reconstruct the complete development history of a software project. <h3>2.2 Manifests</h3> Associated with every check-in is a special file called the [./fileformat.wiki#manifest| "manifest"]. The manifest is a listing of all other files in that source tree. The manifest contains the (complete) artifact ID of the file and the name of the file as it appears on disk, and thus serves as a mapping from artifact ID to disk name. The artifact ID of the manifest is the identifier for the entire check-in. When you look at a "timeline" of changes in fossil, the ID associated with each check-in or commit is really just the artifact ID of the manifest for that check-in. |
| ︙ | ︙ |