On Thu, Nov 10, 2011 at 10:24:45PM +0900, Pieter Hintjens wrote: > On Thu, Nov 10, 2011 at 6:01 AM, Paul Colomiets <p...@colomiets.name> wrote: > > > It may be harder to follow work on github, but not on local copy. just do > > git remote add zeromq2-1 git://github.com/zeromq/zeromq2-1 > > git remote add zeromq2-2 git://github.com/zeromq/zeromq2-2 > > git remote add libzmq git://github.com/zeromq/libzmq > > Pretty much exactly, yes.
I've followed some of the rationale between having different github repos, but not all of it. Couldn't the same thing be accomplished with a single repo and multiple branches, and just implementing different policies on the different branches? ie: master - experimental, unstable head - latest and greatest code master2-1 - 2.1 legacy master3-1 - 3.1 unstable Then do the exact same thing you do now for the 3 separate repos in terms of maintainance and patching and such. It really comes down to preference though and what people expect. Personally, I expect a single project to use a single repo with multiple maintanance branches and feature branches. It's weird and confusing to have to go to different repos depending on which release number I'm currently looking at. As described by Paul above, a developer can make their local git repo look like that, but if it's easier to have them all in a single git repo locally, wouldn't it be easier on github too? Regards, -- AJ Lewis Software Engineer Quantum Corporation Work: 651 688-4346 ---------------------------------------------------------------------- The information contained in this transmission may be confidential. Any disclosure, copying, or further distribution of confidential information is not permitted unless such privilege is explicitly granted in writing by Quantum. Quantum reserves the right to have electronic communications, including email and attachments, sent across its networks filtered through anti virus and spam software programs and retain such messages in order to comply with applicable data security and retention requirements. Quantum is not responsible for the proper and complete transmission of the substance of this communication or for any delay in its receipt. _______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
