4 ms·
https://fossil-scm.org/home/doc/trunk/www/hashpolicy.wiki https://fossil-scm.org/home/doc/trunk/www/hashpolicy.wiki Fossil found a quick way solving this.
by pfix 4y ago
https://fossil-scm.org/home/doc/trunk/www/hashpolicy.wiki https://fossil-scm.org/home/doc/trunk/www/hashpolicy.wiki
Fossil found a quick way solving this.
- fmajid 4y agoLike SQLite, Fossil is an incredibly well-designed jewel of software craftsmanship. It’s unfortunate market dynamics led to git’s dominance instead.
- mdaniel 4y agoMarket dynamics may be true, but the continued use of git has more to do with workflow than implementation. Fossil makes quite a few dogmatic choices and if one buys into them, then fantastic, but it's for sure not a drop-in replacement for the way teams develop software, and thus would require a teamwide "hard fork" This debate comes up every time git and fossil are mentioned in each other's threads
- rst 4y agoLooks like the git project has a different plan for gradual transition -- but one that's more elaborate and somewhat more fragile. Comment from one of the developers (from prior discussion of the same LWN article): https://news.ycombinator.com/item?id=31856133 https://news.ycombinator.com/item?id=31856133