[zeromq-dev] More Questions about C4.1
Luna Duclos
luna.duclos at palmstonegames.com
Wed Jul 1 17:52:13 CEST 2015
You could use one branch per PR and not have this problem.
On Wed, Jul 1, 2015 at 5:44 PM, Paulmichael Blasucci <pblasucci at gmail.com>
wrote:
> So, in general, it's one patch per problem -- which is good. However, the
> way GitHub tacks subsequent commits onto existing pull requests presents a
> bit of a dilemma. Do I keep piling up patches into one big merge? Or do I
> wait for my pull request to be merged before sending over new changes? (or
> am I over-thinking the whole process and/or missing some obvious feature of
> GitHub?)
>
> Thanks!
>
>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20150701/fc7db46c/attachment.htm>
More information about the zeromq-dev
mailing list