> > This is to cope with a github project using bad tag names. The > > recommendation is a version number like v1.25 adding special one off > > cases is not a good idea, get upstream to fix their tagging. > > I'm afraid that's not in option for wide-spread projects, that already > rely on done or other tag naming scheme, like the Intellij IDEA I've > mentioned already. Those do Github releases like crazy, and that's the > way they're. But since the issue itself is minor, I won't insist on > this patch hard. > > > https://help.github.com/articles/creating-releases/ > > > > You can fix the tagging by forking the github project, and tagging > yourself. > > That's more work than just specifying GH_COMMIT instead of GH_TAGNAME > in a port. ;) > > This was my first conversion to GH_ tags and it was messy. I didn't realize something is broken upstream. kirby@ helped me to get it right.
On another note, will somebody please remove me as maintainer? thanks
