>> * Access the Fossil repositories through Git protocol (readonly). > > Intellectually interesting, but, for me, not a selling point as I only use > Git when I have to.
There are lots of software and services that support Git out of the box (e.g., CI services, Go's packages, Rust's crates, Ruby's bundler etc.). And I think this eventually becomes a reason to _not_ use Fossil for projects that need to integrate with these software/services. With a git-protocol layer, I hope to lower down that obstacle. >> * Cheap forking (I have some ideas on how to achieve this in >> Fossil/libfossil). > > Do you mean "cheep cloning"? (In Fossil, the term "fork" is used to describe > an accidental branch created when multiple commits are made against the same > parent. I don't know what other DVCSs call them.) > I meant "forking" in the traditional FOSS sense. Like Ubuntu is a fork of Debian. This one: https://en.wikipedia.org/wiki/Fork_%28software_development%29 By "cheap", I mean, Given "upstream.fossil" which is 1GiB in size fossil clone --cheap file:///path/to/upstream.fossil new-project.fossil results in new-project.fossil which is just a few MiB or less, and it uses upstream.fossil to lookup missing deltas (of course path of upstream.fossil must not change). Git has same concept of "alternate object stores". >> * Cross-fork merge-requests. > > Do you mean pull requests? Yes. > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
