Re: Error in git-cl creating a new issue

2016-01-06 Thread Thomas Morley
2016-01-06 4:07 GMT+01:00 John Gourlay : > I just submitted a small change to the Contributors Guide using git-cl. The > patch got into codereview.appspot.com, but not into > sourceforge.net/p/testlilyissues/issues/. I let git-cl create a new issue for > the patch, but

Re: Error in git-cl creating a new issue

2016-01-06 Thread Simon Albrecht
On 06.01.2016 13:26, Trevor Daniels wrote: John Gourlay, you wrote Wednesday, January 06, 2016 3:07 AM I just submitted a small change to the Contributors Guide using git-cl. The patch got into codereview.appspot.com, but not into sourceforge.net/p/testlilyissues/issues/. I let git-cl

Re: Error in git-cl creating a new issue

2016-01-06 Thread Simon Albrecht
On 06.01.2016 12:48, Thomas Morley wrote: 2016-01-06 4:07 GMT+01:00 John Gourlay : I just submitted a small change to the Contributors Guide using git-cl. The patch got into codereview.appspot.com, but not into sourceforge.net/p/testlilyissues/issues/. I let git-cl

Re: Error in git-cl creating a new issue

2016-01-06 Thread Trevor Daniels
John Gourlay, you wrote Wednesday, January 06, 2016 3:07 AM >I just submitted a small change to the Contributors Guide using git-cl. The >patch got into codereview.appspot.com, but not into >sourceforge.net/p/testlilyissues/issues/. I let git-cl create a new issue for >the patch, but it

Re: Error in git-cl creating a new issue

2016-01-06 Thread Trevor Daniels
Simon Albrecht, you wrote Wednesday, January 06, 2016 1:14 PM > On 06.01.2016 13:26, Trevor Daniels wrote: >> John Gourlay, you wrote Wednesday, January 06, 2016 3:07 AM >> >> >>> I just submitted a small change to the Contributors Guide using git-cl. The >>> patch got into

Re: Error in git-cl creating a new issue

2016-01-06 Thread Simon Albrecht
On 06.01.2016 15:10, Trevor Daniels wrote: Simon Albrecht, you wrote Wednesday, January 06, 2016 1:14 PM On 06.01.2016 13:26, Trevor Daniels wrote: John Gourlay, you wrote Wednesday, January 06, 2016 3:07 AM I just submitted a small change to the Contributors Guide using git-cl. The patch

Re: Error in git-cl creating a new issue

2016-01-06 Thread John Gourlay
I tried to add an issue to the SourceForge issues list by hand, and I got an error email message. Could this be the git-cl problem? The email message says: Your mail to 'Testlilyissues-auto' with the subject [testlilyissues:issues] #4724 Fix typographical errors in Contributor's Guide

Re: Error in git-cl creating a new issue

2016-01-06 Thread Trevor Daniels
Simon, you wrote Wednesday, January 06, 2016 4:05 PM > The rietveld part is fine. Only the Allura part reliably fails, with the > same kind of messages that John reported. > I’ve just been creating issues manually. Well, a 403 HTTP error means the server received and understood the request but

Re: Error in git-cl creating a new issue

2016-01-06 Thread John Gourlay
This was the first time I tried to use git-cl. I made another small typographical fix to the Contributor’s Guide and submitted the new patch. I got the same error. I have the Allura server url set correctly, and I have a bearer token that I obtained following the instructions in the

Error in git-cl creating a new issue

2016-01-05 Thread John Gourlay
I just submitted a small change to the Contributors Guide using git-cl. The patch got into codereview.appspot.com, but not into sourceforge.net/p/testlilyissues/issues/. I let git-cl create a new issue for the patch, but it produced a bunch of error messages. Does anyone have an idea about