Why kernel development still uses email [LWN.net]

Why kernel development still uses email

Posted Oct 14, 2016 19:33 UTC (Fri) by mathstuf (subscriber, #69389)
In reply to: Why kernel development still uses email by Lennie
Parent article: Why kernel development still uses email

The problems arise when non-developers come along to file new issues or comment on old ones. Without some external web or email interface, updating an issue becomes a pull request.

to post comments

Why kernel development still uses email

Posted Oct 20, 2016 18:33 UTC (Thu) by Lennie (subscriber, #49641) [Link] (2 responses)

Sounds like it would be a good idea to create a single binary that can act as a webinterface (& email interface ?) that stores issues-information in git-repositories.

You'd run one on a server where you push the git-repo to for other people to interact with and you can quickly run the binary on your development machine and use the webinterface locally. And are able to do so even offline.

Why kernel development still uses email

Posted Oct 20, 2016 19:42 UTC (Thu) by mathstuf (subscriber, #69389) [Link]

That's pretty much the Fossil SCM in a nutshell (and Veracity too, I think).

Why kernel development still uses email

Posted Apr 28, 2018 19:13 UTC (Sat) by spwhitton (subscriber, #71678) [Link]

ikiwiki works like this (a single binary CGI that can be used online) and can be used as a bug tracker: https://git-annex.branchable.com/bugs/