4 ms·
Or maybe plainly just not a big deal for you, but still problem for others
by adql 4y ago
Or maybe plainly just not a big deal for you, but still problem for others
- zie 4y agoFossil's perspective is deleting/altering and tampering with history is a terrible idea. Some code shops have legal or policy mandates that disallow them from altering history anyway. My employer is such a place. Yes we have a few 'typo' commits that get through, but whatever. In practice it's a non-issue, since Fossil is just a sqlite DB, you can do what amounts to a select * from commits where 'typo' not in commit_msg, and never see them, without doing anything in the second paragraph, which shows you how to do all of this if you are bound and determined. Regardless, if you REALLY want to delete and/or hide history, one can do this in Fossil as well, it's a touch more annoying in Fossil compared to git, but it's not difficult or anything, you can do it all from the CLI. [This thread](https://fossil-scm.org/forum/forumpost/333117081652bf3db6dc6f92ccf6682fd1fcd21f205672c2aad253a5fea6e30a https://fossil-scm.org/forum/forumpost/333117081652bf3db6dc6...) shows hiding branches and commits and [this stackexchange](https://stackoverflow.com/questions/42832992/shun-a-whole-commit-in-fossil https://stackoverflow.com/questions/42832992/shun-a-whole-co...) handles deleting data from the repo.
- CRConrad 4y agoWell, since Fossil stores its stuff in an SQLite database, I'd assume that if you know SQL and the password to your Fossil repo, you can delete and alter history...? After all, SQL consists not only of the SELECT command; it has DELETE and INSERT too.
- zie 4y agoYou can, but your repo would almost certainly not validate well, if it even worked. Just depends on the changes you make I guess.