Ø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? Then when a user does a "git clone", they get them locally and they can do a "git branch" whenever they are motivated to do so. The new git repo is great, for me it takes 15 seconds to clone the whole thing over a not-that-fast ADSL link. I would be quite happy to see some "developer" branches in there (and might easily manage to switch to one occasionally e.g. to try it on my hardware). > I was thinking about committing a script to set up those repositories > in an sf clone. > > E.g. > > git clone sf... > ./setupdevrepositories > git fetch oharboe > git checkout oharboe mrcmcr > > Here ./setupdevrepositories would simply invoke "git remote add XXX". > > Perhaps http://repo.or.cz/w/openocd.git does not need to be much > harder than sf branches? -- John Devereux _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
