Post #2687999

@b0rk@social.jvns.ca this is going to be very useful at $JOB, thank you. In contrast to how git works, I really appreciate Fossil's approach¹: although Fossil's internal storage model is git-compatible², branches-as-sequences-of-commits are first-class objects and can be meaningfully queried, e.g. "what commits come after commit XYZZY?" has O(1) time cost rather than O(n) in the number of refs in the repo. You can attach a wiki page to a branch! ¹: https://fossil-scm.org/home/doc/trunk/www/branching.wiki#tags ²: https://fossil-scm.org/home/doc/trunk/www/inout.wiki