> 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.
I would expect a single repository with major version branches as well. -jeff > > 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 > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
