Øyvind Harboe <[email protected]> writes: > On Tue, Oct 27, 2009 at 2:27 PM, John Devereux <[email protected]> wrote: >> Øyvind Harboe <[email protected]> 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.
Well, one advantage of git is that everyone will have a complete intact copy of the repository. If we have all branches in one, then everyone has a copy of all the branches. > Also the new site allows anyone to set up a repository without asking > anyone for permission. I can see that might be useful. > With a small & clever script, would you really be able to tell > if you used sf or the new site for some dev branch? Well sure, because... git checkout oyvind ...won't work. > My requirement for using the new site is that it should be > no harder than using sf. -- John Devereux _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
