On Mon, Oct 26, 2009 at 8:53 PM, Nicolas Pitre <n...@fluxnic.net> wrote: > On Mon, 26 Oct 2009, David Brownell wrote: > >> 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. > > If that's indicative of anything, on the very Git mailing list (of all > places) about 98% of all changes are posted as patches and merged as > such. No one ever ask people to review patches by fetching a repo.
So here you're really saying that development branches aren't really used, except as a way for maintainers to track patch series? There will be a dozen patches to the mrcmcr stuff before it's "all over" and ready to be committed. What could I realistically expect in terms of testing for the below? - a patch series a dozen patches long - a branch on sf - branch on that other web site in some repository - a branch on that other web site in the "testing" branch of the official testing repository - committed to master branch - some scheme whereby all development branches on all repositories are automatically merged into the "daily pile" that users can test... ? I don't worry about development & branching, git has that sorted. My greatest fear is that we come up with some sort of fancy scheme that gives *zero* testing before stuff is finally committed to the mater branch, which is back to square one really... If there was a simple and obvious answer to this problem of testing and branched development, then we wouldn't be having this discussion. I feel that OpenOCD is special in that for it's size(code and community) it has an insane number of different targets and a huge distance between developers and test hardware. -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
