Re:Fossil: A decentralized version control, bug tracking, an...
by petre on Monday October 10, 2016 @01:07AM
(#12675162)
Fossil does have an undo command but that doesn't work on commits (checkin). It works on update and revert. Also thete is no rebase to edit the history. Once you commit it's there. You just mark the bad commit as a mistake or commit changes in the following checkin. Stuff never gets deleted from the repo but there is a scrub command. All of this encourages one to commit responsibly.
[ Parent
| on HN ]
Re:Fossil: A decentralized version control, bug tracking, an...
by jrapdx3 on Monday October 10, 2016 @01:53AM
(#12675307)
That's interesting an idea in Fossil that I've always assumed was borrowed from database ideology. When data is committed to a database and other data depends on it, deleting data risks damaging data integrity, let alone issues of falsifying the record.
Fossil enforces the ethical principle that history, e.g., of a project, should not be revised after the fact. If broken code is submitted to the repo, it can be replaced, the prior code ignored, but it still is part of the project history, perhaps serving as a reminder of how things can go wrong, often a valuable lesson to pass along.
Projects are like people, we all have warts. We don't have to point them out to casual acquaintances, but we shouldn't try to pretend we don't have them at all.
Re:Fossil: A decentralized version control, bug tracking, an...
by carterehsmith on Monday October 10, 2016 @01:59AM
(#12675323)
Sounds reasonable. Not being able to undo a checkin does not seem like a problem to me, as checkins don't usually bring about ooops moments, if ever.
Also, immutable history makes a lot of sense, not just for SCM, but for RDBMS, too.
So we see quite a few people are now going with the append-only databases.