Re: git cl problem: Couldn’t create Allura issue
On 28.12.2015 23:26, Thomas Morley wrote: 2015-12-28 23:12 GMT+01:00 Simon Albrecht : What does ~/git-cl (master)$ gitk show? For me it returns the attached screenshot (my git-cl is _not_ up to date, working, though) If you're behind the most recent shown commit update it. I’ve got all those commits and some more recent ones. Should really be up to date. Yours, Simon ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: git cl problem: Couldn’t create Allura issue
- Original Message -
From: "Simon Albrecht"
To: "ly-devel"
Sent: Monday, December 28, 2015 10:12 PM
Subject: git cl problem: Couldn’t create Allura issue
Hello,
sorry, but I still don’t seem to get along with git cl. I just uploaded a
patch and it went fine until:
~/lilypond-git (dev/doc)$ git cl upload origin/master
Documentation/learning/common-notation.itely | 25
+++--
1 file changed, 23 insertions(+), 2 deletions(-)
Upload server: codereview.appspot.com (change with -s/--server)
Your browser has been opened to visit:
https://codereview.appspot.com/get-access-token?port=8001
If your browser is on a different machine then exit and re-run
upload.py with the command-line parameter
--no_oauth2_webbrowser
Issue created. URL: http://codereview.appspot.com/280560043
Uploading base file for Documentation/learning/common-notation.itely
We were not able to associate this patch with a tracker issue.
Please enter a valid tracker issue number
(or enter nothing to create a new issue):
Error code 403
The config seems to be OK: (I hid the bearer token)
~/lilypond-git (dev/doc)$ git cl config
Rietveld server (host[:port]) [codereview.appspot.com]:
Allura server [http://sourceforge.net/p/testlilyissues/issues/]:
Allura bearer token (see https://sourceforge.net/auth/oauth/) []:
CC list ("x" to clear) [lilypond-devel@gnu.org]:
Yours, Simon
I'm wondering if this is just a co-incidence: sourceforge seems slow
currently.
Anyway, I've endeavoured to add a little more information if this command
fails. Please pull.
--
Phil Holmes
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: git cl problem: Couldn’t create Allura issue
On 29.12.2015 15:38, Phil Holmes wrote:
- Original Message - From: "Simon Albrecht"
To: "ly-devel"
Sent: Monday, December 28, 2015 10:12 PM
Subject: git cl problem: Couldn’t create Allura issue
Hello,
sorry, but I still don’t seem to get along with git cl. I just
uploaded a patch and it went fine until:
~/lilypond-git (dev/doc)$ git cl upload origin/master
Documentation/learning/common-notation.itely | 25
+++--
1 file changed, 23 insertions(+), 2 deletions(-)
Upload server: codereview.appspot.com (change with -s/--server)
Your browser has been opened to visit:
https://codereview.appspot.com/get-access-token?port=8001
If your browser is on a different machine then exit and re-run
upload.py with the command-line parameter
--no_oauth2_webbrowser
Issue created. URL: http://codereview.appspot.com/280560043
Uploading base file for Documentation/learning/common-notation.itely
We were not able to associate this patch with a tracker issue.
Please enter a valid tracker issue number
(or enter nothing to create a new issue):
Error code 403
The config seems to be OK: (I hid the bearer token)
~/lilypond-git (dev/doc)$ git cl config
Rietveld server (host[:port]) [codereview.appspot.com]:
Allura server [http://sourceforge.net/p/testlilyissues/issues/]:
Allura bearer token (see https://sourceforge.net/auth/oauth/)
[]:
CC list ("x" to clear) [lilypond-devel@gnu.org]:
Yours, Simon
I'm wondering if this is just a co-incidence: sourceforge seems slow
currently.
Indeed. I’ll make more attempts then. It just failed in the very same
way (forgot to pull git-cl beforehand), so I created the allura issue
manually in order to not clutter the Rietveld issue with more identical
patch sets. Perhaps git cl could be enhanced with options to do only the
Rietveld or Allura parts of the process?
Yours, Simon
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: git cl problem: Couldn’t create Allura issue
- Original Message -
From: "Simon Albrecht"
To: "Phil Holmes" ; "ly-devel"
Sent: Tuesday, December 29, 2015 4:19 PM
Subject: Re: git cl problem: Couldn’t create Allura issue
On 29.12.2015 15:38, Phil Holmes wrote:
- Original Message - From: "Simon Albrecht"
To: "ly-devel"
Sent: Monday, December 28, 2015 10:12 PM
Subject: git cl problem: Couldn’t create Allura issue
Hello,
sorry, but I still don’t seem to get along with git cl. I just uploaded a
patch and it went fine until:
~/lilypond-git (dev/doc)$ git cl upload origin/master
Documentation/learning/common-notation.itely | 25
+++--
1 file changed, 23 insertions(+), 2 deletions(-)
Upload server: codereview.appspot.com (change with -s/--server)
Your browser has been opened to visit:
https://codereview.appspot.com/get-access-token?port=8001
If your browser is on a different machine then exit and re-run
upload.py with the command-line parameter
--no_oauth2_webbrowser
Issue created. URL: http://codereview.appspot.com/280560043
Uploading base file for Documentation/learning/common-notation.itely
We were not able to associate this patch with a tracker issue.
Please enter a valid tracker issue number
(or enter nothing to create a new issue):
Error code 403
The config seems to be OK: (I hid the bearer token)
~/lilypond-git (dev/doc)$ git cl config
Rietveld server (host[:port]) [codereview.appspot.com]:
Allura server [http://sourceforge.net/p/testlilyissues/issues/]:
Allura bearer token (see https://sourceforge.net/auth/oauth/) []:
CC list ("x" to clear) [lilypond-devel@gnu.org]:
Yours, Simon
I'm wondering if this is just a co-incidence: sourceforge seems slow
currently.
Indeed. I’ll make more attempts then. It just failed in the very same
way (forgot to pull git-cl beforehand), so I created the allura issue
manually in order to not clutter the Rietveld issue with more identical
patch sets. Perhaps git cl could be enhanced with options to do only the
Rietveld or Allura parts of the process?
Yours, Simon
=
I think it is intended to, but I may have destroyed that capability during
the updates.
--
Phil Holmes
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
