News for hackers. Stuff that matters.

A comment on Fossil: A decentralized version control, bug tracking, and wiki software. Parent comment

Re:Fossil: A decentralized version control, bug tracking, an... by carterehsmith on Monday October 10, 2016 @05:01PM (#12679755)
> common way to get the effect you want with Fossil is to mark the bad commit as the start of a new branch, then resume work on the previously-damaged branch

Would it not be easier to just say "rollback"? Note that a "rollback" would apply just to the things changed since the last commit, just like in SQL. So then, by definition, you cannot rollback a commit. Just like in SQL.

[ Parent | on HN ]
Re:Fossil: A decentralized version control, bug tracking, an... by wyoung2 on Monday October 10, 2016 @07:13PM (#12680522)
> just like in SQL.

Which SQL dialect are you using where you can ROLLBACK after COMMIT? That isn't ANSI SQL-92 or SQLite behavior. Quoting the standard:

> An SQL-transaction is terminated by a <commit statement> or a <rollback statement>.

Perhaps you were thinking of savepoints?

[ Parent | on HN ]