On Tue, 27 Oct 2009, Øyvind Harboe wrote: > On Tue, Oct 27, 2009 at 2:27 PM, John Devereux <j...@devereux.me.uk> wrote: > > Øyvind Harboe <oyvind.har...@zylin.com> writes: > > > >> From a developer point of view, I'm satisified with pushing dev branches > >> to http://repo.or.cz/w/openocd.git. I have not yet used a shared developer > >> branch... Who in their right mind would get involved in the mrcmcr branch? > >> :-) > >> > >> I would like to see users test those branches though... What's the > >> best way to make that happen? > > > > Isn't the best way to just simply have the branches in the main > > repository? > > It's the best, until something goes horribly wrong.
Like what? Someone messes up the master branch? There are ways to mitigate that risk. And in the worst case you have plenty of full backups all around the globe already. > Also the > new site allows anyone to set up a repository without asking > anyone for permission. That still can be done. There is no incompatibility with the idea of having more significant development branches offered for free to users through the main repository, and people like myself putting proposed work in a separate repo until it is made available through the main repo in a branch of its own, or pulled into the master branch, or rejected outright. > With a small & clever script, would you really be able to tell > if you used sf or the new site for some dev branch? It's the principle of asking users to use an otherwise unneeded script to achieve the same result that somehow bothers me. Nicolas
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
