Fossil checkout database
(Created page with "{{FormatInfo |formattype=electronic |subcat=Development |released=2006<ref>Wikipedia:Fossil (software)</ref> }} The version control software Fossil separates the working d...") |
m (Added link for "version control") |
||
Line 4: | Line 4: | ||
|released=2006<ref>[[Wikipedia:Fossil (software)]]</ref> | |released=2006<ref>[[Wikipedia:Fossil (software)]]</ref> | ||
}} | }} | ||
− | 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"<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" /> |
== Links == | == Links == |
Revision as of 05:04, 3 August 2019
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]
Links
See Also
- Fossil repository database
- Fossil configuration database
- Fossil (unrelated filesystem)
- FOSSIL (unrelated set of networking protocols)
References
- ↑ Wikipedia:Fossil (software)
- ↑ 2.0 2.1 https://fossil-scm.org/home/doc/trunk/www/tech_overview.wiki → 2.3 Checkout Databases