[zeromq-dev] 0MQ/3.0, 0MQ/4.0 and 0MQ process

Mikko Koppanen mikko.koppanen at gmail.com
Mon Oct 31 00:00:10 CET 2011


On Sun, Oct 30, 2011 at 10:48 PM, Martin Lucina <martin at lucina.net> wrote:
> A couple more points:
>
> Regarding pull requests vs. patches. Martin's main problem with the Github
> interface to pull requests is that it is not transparent to the entire
> community. One way to make that work is to go back to Linus Torvalds'
> original idea of what a pull request is:
>
>  - A pull request is simply an email to the project mailing list, asking
>   the maintainer to please pull all commits from branch X of repository Y.
>   It is assumed that such a branch is effectively a topic branch, and has
>   been rebased to merge cleanly against the current master.

Hello,

I'm not an expert in the field but I would like to chip in on this.
The github interface is a just a convenience on top pull requests and
provides things like syntax highlighted diffs, shows whether the
commit merges cleanly, allows commenting etc.

If the problem with the interface is that it's not visible to users on
mailing-lists, we can most probably use github API to send an email to
mailing-lists when a new pull request is opened. I like the github
interface a lot and would like to see us using it more.

-- 
Mikko Koppanen



More information about the zeromq-dev mailing list