4 ms·
in terms of Fossil as an SCM, it's very similar outside of the author's views of rebase (which I happen to agree with). https://fossil-scm.org/home/doc/trunk/w
by PH95VuimJjqBqy 3y ago
in terms of Fossil as an SCM, it's very similar outside of the author's views of rebase (which I happen to agree with).
https://fossil-scm.org/home/doc/trunk/www/rebaseharm.md https://fossil-scm.org/home/doc/trunk/www/rebaseharm.md
In terms of Fossil as a technology, it's an SCM with built-in project management tools (wiki, forums, bug tracker, etc) so it does much more than git does.
The front page has more info:
https://fossil-scm.org/home/doc/trunk/www/index.wiki https://fossil-scm.org/home/doc/trunk/www/index.wiki
- wrkta 3y agoI don't really agree with this assessment of rebase. I think there is value in squashing commits on dev branches into logically distinct sets to keep the log cleaner. In the case where the reason code is doing something that is not obvious I think that explaining the reasoning or the journey to that point in a commit message is clearer than the complete history of trial and error to reach that state.
- PH95VuimJjqBqy 3y agoThis is one of those things where both sides have a point based upon their values as developers.