lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: git cl


From: James
Subject: Re: git cl
Date: Tue, 6 Oct 2015 12:19:48 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]