Phil, On 06/10/15 12:32, Phil Holmes wrote: > ----- Original Message ----- From: "James" <p...@gnu.org> > To: "Phil Holmes" <m...@philholmes.net>; <lilypond-devel@gnu.org> > Sent: Tuesday, October 06, 2015 12:19 PM > Subject: Re: git cl > > >> Phil, >> >> On 05/10/15 16:19, Phil Holmes wrote: >>> I now have git-cl mostly working with the Allura issue tracker. Please >>> note that I've not really followed any coding standards, the error >>> handling is rudimentary to say the least, and any competent Python >>> programmer would prbably have kittens over some of what I've done. >>> However, it does allow new issues to be created for new patches, and >>> existing patch issues to be updated. >>> >>> You should be able to use it by pulling from the git-cl repository, and >>> immediately running "git cl config". As part of the configuration you >>> will need to supply a "bearer token", which uniquely identifies >>> you. You >>> make one at https://sourceforge.net/auth/oauth/ by adding an >>> application >>> (I used one called git-cl). >>> >>> Trevor has requested one enhancement: setting the owner if someone >>> starts >>> work on an old issue with a new patch. I suggest we start a tracker >>> for >>> enhancement and bug reports for git-cl and I'll work on them as I can. >> What is the URL that you need to enter when running git-cl config? >> >> At the moment (unlike the rietveld URL) nothing is listed as default. >> >> Is it >> >> https://sourceforge.net/projects/testlilyissues/ >> >> or something else? >> >> James >> > > Not quite. It's the full link to the issues list: > https://sourceforge.net/p/testlilyissues/issues/ Thanks, that seems to work, sort of ;)
I've updated one of my own tickets. https://sourceforge.net/p/testlilyissues/issues/4619/ But the Patch didn't change from 'Countdown' to 'New' - it's still 'Countdown'. James _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
