On Tue, 2 Feb 2010 11:31:12 +1300, martin f krafft <madd...@madduck.net> wrote: > Arguably, being patch-centric means that a project has a higher > barrier of entry, but it also means that if someone wants something, > they know that they'll have to somehow end up with a patch. The way > this happens on Git is that you either write it yourself and bring > it up to discussion (which is what patchwork facilitates), or > constructively theorise the functionality until someone else > submits a patch.
And don't forget, if you really want something on the longterm todo list, you can always send in a patch for the TODO file. ;) -- - Marten _______________________________________________ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
