On 09:22 Mon 11 Jul , Spencer Oliver wrote: > On 11 July 2011 07:31, Jean-Christophe PLAGNIOL-VILLARD > <plagn...@jcrosoft.com> wrote: > >> Totally agree on this - FreeBSD ports use automatic package download > >> and extraction mechanism, so having tarball for RC2 would be great! > >> Please let me know then its available :-) > > for RC we have us gitweb to generate the tar.bz > > > > > > rc1 > > > > http://openocd.git.sourceforge.net/git/gitweb.cgi?p=openocd/openocd;a=snapshot;h=ff640f197a9a343b2f3ed10e9174e35282334e8c;sf=tgz > > > > rc2 > > > > http://openocd.git.sourceforge.net/git/gitweb.cgi?p=openocd/openocd;a=snapshot;h=d4cd6f032015552f00bf4b5a90f25f5f958e9d9e;sf=tgz > > > > But these are not really a real release, created by make dist. > Surely we should be running make dist then uploading the releases to > sourceforge/berlios etc. > > Have you had a look at tools/release.sh? I did, as we have nothing for rc3 I'll use it for the first tarball release and will push the tarball on sf.net
if for the rc4 we have nothing again we will post pone it for one week Best Regards, J. _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
