|
|
|
|
|
|
by leschak
929 days ago
|
|
|
100% fossil. there has been a few threads.. and always someone points out edge cases that are only to be solved using git.. well i dont think so. you can actually go into the sqlite db and change stuff. i've recently started playing with its server api to direct user feedback from web to fossils ticketing system. it is just mature and feature packed and i honestly hope it will get as much recognition as sqlite someday. |
|
|
_Nothing_ history-relevant can be changed via manipulation of the Fossil db. In terms of db records, as opposed to space, the db is about 80-90% a transient cache of data which is generated from the remaining (100% immutable) data. Any changes you make to that transient data will be lost the next time that cache is discarded and rebuilt. A longer explanation can be found at:
https://fossil-scm.org/home/doc/trunk/www/fossil-is-not-rela...