A simpler alternative to having a dedicated pull-request feature in fossil is to just have a second "free-for-all" repository where commit capability is granted to pretty much any passerby willing to fill out a CAPTCHA and register an account. Said passerby can then just use the ticket system (or a mailing list, or the built-in forum that drh seems to have started working on) to notify the main repository developers that a pull-request exists on some particular branch in the free-for-all repository. A developer on the main repository then uses `fossil bundle` (or some improved version thereof) to import the changes on that specific branch into the main repository, possibly altering them in the process (i.e. by importing the bundle as a private branch, then "rebasing" or compressing the changes onto a different public branch).
The comments Florian and I made about `bundle import` security still apply, though. There needs to be some way for a developer to ensure the bundle they're importing will not "spray" checkins and control artifacts all over the repository. By the way, the current `bundle ls` implementation just trusts the `notes` column of the `bblob` table; it doesn't actually check the blob contents. Best, Eduard _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
