Fossil checkout database
m (Added link for "version control") |
(Category:SQLite based file formats) |
||
| (One intermediate revision by one user not shown) | |||
| Line 5: | Line 5: | ||
}} | }} | ||
The [[Development#Revision control systems / code repositories|version control]] software Fossil separates the working directory, where edits to the version-controlled data are made, and the repository, where version history is kept; this is different from systems like [[Git]], where the database with version history is a subdirectory of the working directory. As such, metadata about the working directory is not stored in the repository, and instead in a file called the "'''checkout database'''", which does reside in the working directory. The checkout database is (like the repository database) [[SQLite]]-based, and it has the name "_FOSSIL_" or ".fslckout"<ref name="doc">https://fossil-scm.org/home/doc/trunk/www/tech_overview.wiki → 2.3 Checkout Databases</ref>. A Fossil command will look for the checkout database by moving up towards the filesystem root and checking for the presence of a file with the proper name; it will stop searching on the first matching file it finds.<ref name="doc" /> | The [[Development#Revision control systems / code repositories|version control]] software Fossil separates the working directory, where edits to the version-controlled data are made, and the repository, where version history is kept; this is different from systems like [[Git]], where the database with version history is a subdirectory of the working directory. As such, metadata about the working directory is not stored in the repository, and instead in a file called the "'''checkout database'''", which does reside in the working directory. The checkout database is (like the repository database) [[SQLite]]-based, and it has the name "_FOSSIL_" or ".fslckout"<ref name="doc">https://fossil-scm.org/home/doc/trunk/www/tech_overview.wiki → 2.3 Checkout Databases</ref>. A Fossil command will look for the checkout database by moving up towards the filesystem root and checking for the presence of a file with the proper name; it will stop searching on the first matching file it finds.<ref name="doc" /> | ||
| + | |||
| + | The application ID for a Fossil repository database is 252006674. | ||
== Links == | == Links == | ||
| Line 19: | Line 21: | ||
<references /> | <references /> | ||
| + | [[Category:SQLite based file formats]] | ||
[[Category:File formats with a distinctive filename]] | [[Category:File formats with a distinctive filename]] | ||
Latest revision as of 14:27, 10 February 2020
The version control software Fossil separates the working directory, where edits to the version-controlled data are made, and the repository, where version history is kept; this is different from systems like Git, where the database with version history is a subdirectory of the working directory. As such, metadata about the working directory is not stored in the repository, and instead in a file called the "checkout database", which does reside in the working directory. The checkout database is (like the repository database) SQLite-based, and it has the name "_FOSSIL_" or ".fslckout"[2]. A Fossil command will look for the checkout database by moving up towards the filesystem root and checking for the presence of a file with the proper name; it will stop searching on the first matching file it finds.[2]
The application ID for a Fossil repository database is 252006674.
[edit] Links
[edit] See Also
- Fossil repository database
- Fossil configuration database
- Fossil (unrelated filesystem)
- FOSSIL (unrelated set of networking protocols)
[edit] References
- ↑ Wikipedia:Fossil (software)
- ↑ 2.0 2.1 https://fossil-scm.org/home/doc/trunk/www/tech_overview.wiki → 2.3 Checkout Databases
