On Monday 26 October 2009, Zach Welch wrote: > > There are few good reasons to do active branch development in the main > repository. I established the openocd/testing fork on repo.or.cz to do > exactly what you describe. Setting this up requires adding that remote > one time, and everyone can create a fork to push.
Any developer can also set up their own public repo at SF, if they're part of the OpenOCD project. Or any other git hosting service, of course... I suppose I would prefer to do that than "dirty" the main tree with branches that aren't part of the release cycle, and are more in the "playpen" mode than the "pre-merge" mode. Note by the way that public repositories are mostly for publishing work you expect others to use. I'm not sure I'd expect folk to review patches from repositories as any kind of regular thing ... it may be marginally easier to do that way than sending them on the mailing lists. - Dave _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
