Much better :) hans@dhcp-10 src $ git fetch --tags >From git://pure-data.git.sourceforge.net/gitroot/pure-data/pure-data * [new tag] 0.32-1test5 -> 0.32-1test5 * [new tag] 0.41-0test06 -> 0.41-0test06 * [new tag] 0.42-4 -> 0.42-4 * [new tag] 0.42-5 -> 0.42-5 * [new tag] 0.43-1 -> 0.43-1 * [new tag] 0.43-1test3 -> 0.43-1test3 * [new tag] 0.43-1test4 -> 0.43-1test4 * [new tag] 0.43-2 -> 0.43-2 * [new tag] 0.43-2test1 -> 0.43-2test1 * [new tag] 0.43-3 -> 0.43-3 * [new tag] 0.43-3test1 -> 0.43-3test1 * [new tag] 0.43-4 -> 0.43-4 * [new tag] 0.43-test1 -> 0.43-test1 * [new tag] tmp -> tmp
Looks like 0.32-1test5 is supposed to be 0.43-1test5, since its between 0.43-1test4 and 0.43-1. .hc On Oct 8, 2012, at 1:33 AM, Miller Puckette wrote: > Funny - I'd been tagging away but never realized they weren't getting > pushed (didn't know about the 'tags' option) - see what it looks like to you > now. > > chers > Miller > > On Sun, Oct 07, 2012 at 08:36:43PM -0400, Hans-Christoph Steiner wrote: >> >> Hey Miller, >> >> It would be very useful to have tags in your pure-data.git repo so its easy >> to find the releases. I'm happy to do the tagging and uploading to the >> official repo, or you can do it: >> >> git tag 0.43.3 49d7e9c997afc3bfce8ce2ffea8a7c06a541d146 >> git tag 0.43.2 f24b62367300bac7345651da50d991b88af1dfae >> ... >> git push --tags >> >> Or to download the tags: >> >> git fetch --tags >> >> .hc >> _______________________________________________ >> Pd-dev mailing list >> Pd-dev@iem.at >> http://lists.puredata.info/listinfo/pd-dev _______________________________________________ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
