[zeromq-dev] 0MQ/3.0, 0MQ/4.0 and 0MQ process
Mikko Koppanen
mikko.koppanen at gmail.com
Sun Oct 30 01:39:26 CEST 2011
On Sat, Oct 29, 2011 at 4:44 PM, Pieter Hintjens <ph at imatix.com> wrote:
> Github doesn't allow forking of repos within the same organization,
> which was the reason we created separate repos per main version. The
> separate gits allowed different processes per version which IMO has
> worked very well. E.g. patches to ML for libzmq, pull requests for
> zeromq2-1. All we've lost is a single history, which really no-one has
> ever proven necessary.
Hi,
from contributors (my) view the multiple repos and processes has never
worked really well. There is certain amount of confusion of how to get
patch into different repositories and how to follow a patch throughout
different versions.
I am all in (as I have been always) for single repository and single
process for all the development. There should be no need to create
multiple forks inside a single organisation for things that can be
done in branches inside a single repository.
--
Mikko Koppanen
More information about the zeromq-dev
mailing list