Re: dowloading git-cl, connection timed out

Hi, Gérard, welcome to the list. Le dimanche 10 septembre 2023 à 21:47 +0200, pubabhervegueg...@free.fr a écrit : > > > Thank you David for your answer. > > git-cl is part of setup.sh I downloaded on 2023-08-17 from > LilyDev-2-debian-vm.zip. > > Should I have down

Re: dowloading git-cl, connection timed out

Thank you David for your answer. git-cl is part of setup.sh I downloaded on 2023-08-17 from LilyDev-2-debian-vm.zip. Should I have downloaded instead Lilydev 3, and are there precise instructions of how to use it, maybe with Docker? Thank you much again, Gerard Le 2023-09-10 19:28

Re: dowloading git-cl, connection timed out

pending on instrument schools), I do > no expect to find a community already or wishing to work on the > subject up now. > > But I face a beginner's problem: timeout on git-cl download > > I am following 2.25.7 Lilypond Contributor's guide, > I Installed the proposed Debian 11 f

dowloading git-cl, connection timed out

a community already or wishing to work on the subject up now. But I face a beginner's problem: timeout on git-cl download I am following 2.25.7 Lilypond Contributor's guide, I Installed the proposed Debian 11 from zip on Oracle VM Virtualbox, my host is Windows10 secured by default Windows Defender

git-cl: Problem setting 'owner' field

Folks, I can use `git-cl` just fine. However, I always get the message Problem setting patch status for Allura issue and the 'owner' field of the created SF issue is not properly set. Any idea how to fix this? Werner

Re: git-cl patch: remove some redundant text from tracker fields

Done a few seconds ago. -- Phil Holmes - Original Message - From: "James" To: Sent: Saturday, November 23, 2019 9:48 AM Subject: Re: git-cl patch: remove some redundant text from tracker fields Looks like this hasn't been merged yet. On 15/11/2019 15:15, Dan Eble wro

Re: git-cl patch: remove some redundant text from tracker fields

. https://github.com/gperciva/git-cl/pull/6 Thanks, — Dan

git-cl patch: remove some redundant text from tracker fields

Please review. This handles a couple of details I'd rather not have to remember to do when submitting the patch or fix after the fact. I've exercised these changes for the last few LilyPond patches I've uploaded. https://github.com/gperciva/git-cl/pull/6 Thanks, — Dan

Re: git-cl command not found

Il giorno gio 14 nov 2019 alle 20:56, David Nalesnik ha scritto: It's not in your PATH ? Ah yes. Duh. Didn't think to check b/c I figured this would just work out of the box. It should work out of the box, see:

Re: git-cl command not found

On Thu, Nov 14, 2019 at 7:05 PM David Kastrup wrote: > > David Nalesnik writes: > > > Trying to get git-cl going I run into an interesting problem. I've > > installed LilyDev, so I should have git-cl. > > > > I update: > > [dev@lilydev:lilypond-git]$ cd

Re: git-cl command not found

David Nalesnik writes: > Trying to get git-cl going I run into an interesting problem. I've > installed LilyDev, so I should have git-cl. > > I update: > [dev@lilydev:lilypond-git]$ cd ~/git-cl/ > [dev@lilydev:git-cl]$ git pull > remote: Enumerating objects: 4, done. >

git-cl command not found

Trying to get git-cl going I run into an interesting problem. I've installed LilyDev, so I should have git-cl. I update: [dev@lilydev:lilypond-git]$ cd ~/git-cl/ [dev@lilydev:git-cl]$ git pull remote: Enumerating objects: 4, done. remote: Counting objects: 100% (4/4), done. remote: Compressing

Re: git-cl upload and existing sf issues

On Nov 2, 2019, at 12:35, Dan Eble wrote: > >> when uploading a first patch set, git-cl asks for a sourceforge issue >> number. If a new issue is created, everything is fine but when you choose an >> existing issue, there is some 404 error and the Rietveld link is not adde

Re: git-cl upload and existing sf issues

On Sep 30, 2019, at 16:54, Malte Meyn wrote: > > when uploading a first patch set, git-cl asks for a sourceforge issue number. > If a new issue is created, everything is fine but when you choose an existing > issue, there is some 404 error and the Rietveld link is not added to the

git-cl upload and existing sf issues

Hi list, when uploading a first patch set, git-cl asks for a sourceforge issue number. If a new issue is created, everything is fine but when you choose an existing issue, there is some 404 error and the Rietveld link is not added to the sf issue—resulting in a missing Rietveld link

Re: git-cl: "Update attempt returns error code 404"

Il giorno dom 9 dic 2018 alle 11:42, Federico Bruni ha scritto: Il giorno sab 8 dic 2018 alle 16:52, Malte Meyn ha scritto: Hi list, I just uploaded a patch for issue 2575 and got the following git-cl messages: […] Issue created. URL: http://codereview.appspot.com/341520043

Re: git-cl: "Update attempt returns error code 404"

Il giorno sab 8 dic 2018 alle 16:52, Malte Meyn ha scritto: Hi list, I just uploaded a patch for issue 2575 and got the following git-cl messages: […] Issue created. URL: http://codereview.appspot.com/341520043 Uploading base file for input/regression/ambitus-middleC.ly Uploading base

git-cl: "Update attempt returns error code 404"

Hi list, I just uploaded a patch for issue 2575 and got the following git-cl messages: […] Issue created. URL: http://codereview.appspot.com/341520043 Uploading base file for input/regression/ambitus-middleC.ly Uploading base file for lily/ambitus-engraver.cc This has been identified

git cl 404 error

Hi, trying to upload a revised patch-set for Issue 5437 via $ git cl upload origin/master I get a 404 error Full terminal-output: $ git cl upload origin/master scm/markup.scm | 66 +- 1 file changed, 41 insertions(+), 25 deletions

git-cl upload: fontconfig and Google Chrome errors

Hi all I've just sent a patch for review using git-cl and I got below two errors. Why git-cl cares for fontconfig? There's also an error related to Google Chrome (the browser I use to log in to Google services). I haven't investigated, since I'm on a very slow Internet connection

Re: patch for git-cl

2017-01-09 0:09 GMT+01:00 Graham Percival <gra...@percival-music.ca>: > On Sun, Jan 08, 2017 at 09:02:51PM +, Thomas Morley wrote: >> attached a little patch for git-cl to replace googlecodeissue by >> trackerissue in cl_settings.py, which will result in correct i

Re: patch for git-cl

On Sun, Jan 08, 2017 at 09:02:51PM +, Thomas Morley wrote: > attached a little patch for git-cl to replace googlecodeissue by > trackerissue in cl_settings.py, which will result in correct info in > .git/config > > How do we handle patches to git-cl? In general, I'd recommend

Re: patch for git-cl

On Sun, Jan 08, 2017 at 10:15:24PM +, James wrote: > On Sun, 8 Jan 2017 21:02:51 + > Thomas Morley <thomasmorle...@gmail.com> wrote: > > > attached a little patch for git-cl to replace googlecodeissue by > > trackerissue in cl_settings.py, which will result

Re: patch for git-cl

On Sun, 8 Jan 2017 21:02:51 + Thomas Morley <thomasmorle...@gmail.com> wrote: > Hi, > > attached a little patch for git-cl to replace googlecodeissue by > trackerissue in cl_settings.py, which will result in correct info in > .git/config > > How do we handle pat

patch for git-cl

Hi, attached a little patch for git-cl to replace googlecodeissue by trackerissue in cl_settings.py, which will result in correct info in .git/config How do we handle patches to git-cl? Cheers, Harm From b8364652a91f3e07bef7719da71f56994c69e7b3 Mon Sep 17 00:00:00 2001 From: Thomas Morley

Issue 4888: git-cl: update status to Started for existing issues (issue 301920043 by nine.fierce.ball...@gmail.com)

Reviewers: , Description: Issue 4888: git-cl: update status to Started for existing issues Please review this at https://codereview.appspot.com/301920043/ Affected files (+1, -0 lines): M allura_issues.py Index: allura_issues.py diff --git a/allura_issues.py b/allura_issues.py index

Re: git-cl problem

Il giorno ven 27 mag 2016 alle 1:59, John Gourlay <j...@weathervanefarm.net> ha scritto: I believe my git-cl problem was due to an incorrect setting in my Google Account Settings. I was not allowing access by “less secure” apps as described in Contributor’s Guide, section 2.3. I

Re: git-cl problem

I believe my git-cl problem was due to an incorrect setting in my Google Account Settings. I was not allowing access by “less secure” apps as described in Contributor’s Guide, section 2.3. I wonder if the CG should be revised, because it implies that “allowed” is the default, but in my case

Re: Doc: Contrib 2.3 Updating git-cl - change source directory (issue 299880043 by gre...@fastmail.co.uk)

On 2016/05/07 11:05:56, Carl wrote: So this patch should be abandoned aND the issue marked invalid, right? Thanks, Carl Yes, correct. I hope I've done this correctly on the issue tracker... https://codereview.appspot.com/299880043/ ___

Re: Doc: Contrib 2.3 Updating git-cl - change source directory (issue 299880043 by gre...@fastmail.co.uk)

So this patch should be abandoned aND the issue marked invalid, right? Thanks, Carl https://codereview.appspot.com/299880043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Doc: Contrib 2.3 Updating git-cl - change source directory (issue 299880043 by gre...@fastmail.co.uk)

So this patch should be abandoned aND the issue marked invalid, right? Thanks, Carl https://codereview.appspot.com/299880043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Doc: Contrib 2.3 Updating git-cl - change source directory (issue 299880043 by gre...@fastmail.co.uk)

#newcode501 Documentation/contributor/quick-start.itexi:501: cd ~/src/git-cl/ That's not where my git-cl repository is, and I don't know whether anyone else's is. Why do you suggest this change? Hi both. I made the change because I downloaded LilyDev from (http://www.et.byu.edu/~sorensen/ubuntu

Re: Doc: Contrib 2.3 Updating git-cl - change source directory (issue 299880043 by gre...@fastmail.co.uk)

#newcode501 Documentation/contributor/quick-start.itexi:501: cd ~/src/git-cl/ That's not where my git-cl repository is, and I don't know whether anyone else's is. Why do you suggest this change? All the CG manual assumes that this stuff (including lilypond-git) is in the home directory. And LilyDev

Re: Doc: Contrib 2.3 Updating git-cl - change source directory (issue 299880043 by gre...@fastmail.co.uk)

-start.itexi:501: cd ~/src/git-cl/ That's not where my git-cl repository is, and I don't know whether anyone else's is. Why do you suggest this change? https://codereview.appspot.com/299880043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https

Doc: Contrib 2.3 Updating git-cl - change source directory (issue 299880043 by gre...@fastmail.co.uk)

Reviewers: , Description: Doc: Contrib 2.3 Updating git-cl - change source directory Change the directory in which the user must run `git pull` to update git-cl Please review this at https://codereview.appspot.com/299880043/ Affected files (+1, -1 lines): M Documentation/contributor/quick

Re: git-cl problem

- Original Message - From: "David Kastrup" <d...@gnu.org> To: "John Gourlay" <j...@weathervanefarm.net> Cc: "Phil Holmes" <m...@philholmes.net>; "LilyPond Development Team" <lilypond-devel@gnu.org> Sent: Tuesday, Ma

Re: git-cl problem

John Gourlay <j...@weathervanefarm.net> writes: > My git-cl seems to be up to date. When I do “git pull” in my git-cl > directory it says, “Already up-to-date.” A couple of months ago I was > unable to use git-cl to create a new issue. I haven’t tried recently, > but t

Re: git-cl problem

My git-cl seems to be up to date. When I do “git pull” in my git-cl directory it says, “Already up-to-date.” A couple of months ago I was unable to use git-cl to create a new issue. I haven’t tried recently, but the symptom appears to be the same whether the issue is new or old. Of course, I

Re: git-cl problem

I don't know of one. Just after Christmas I updated git-cl to add some more information if it failed: are you using the latest version? Also - can you run git-cl with a new issue? -- Phil Holmes - Original Message - From: "John Gourlay" <j...@weathervanefarm.net>

Re: git-cl problem

<j...@weathervanefarm.net> > To: "LilyPond Development Team" <lilypond-devel@gnu.org> > Sent: Tuesday, May 03, 2016 1:25 AM > Subject: Re: git-cl problem > > >> Phil, >> >> Actually, my copy of Contributor’s Guide in section 3.2.2 says to us

Re: git-cl problem

- Original Message - From: "John Gourlay" <j...@weathervanefarm.net> To: "LilyPond Development Team" <lilypond-devel@gnu.org> Sent: Tuesday, May 03, 2016 1:25 AM Subject: Re: git-cl problem Phil, Actually, my copy of Contributor’s Guide in section 3

Re: git-cl problem

Phil, Actually, my copy of Contributor’s Guide in section 3.2.2 says to use “git-cl upload master”. But, you raise a good point. I have already merged my changes from my philomelos branch into my master branch. If git-cl is comparing those two branches it won’t find a difference

Re: git-cl problem

John, Did you try running git-cl in a terminal? I guess that this is an Emacs problem. On Fri, Apr 29, 2016 at 08:34:18PM -0400, John Gourlay wrote: > Carl, > > Yes, I can and frequently do run git itself from the command line. To use > your example: > > [lilypond-git (p

Re: git-cl problem

- Original Message - From: "John Gourlay" <j...@weathervanefarm.net> To: "Federico Bruni" <f...@inventati.org> Cc: "LilyPond Development Team" <lilypond-devel@gnu.org> Sent: Monday, May 02, 2016 3:37 PM Subject: Re: git-cl problem Federi

Re: git-cl problem

Federico, I am running git-cl in a terminal window. I changed my default editor to leafpad. When I run git-cl again the emacs warning is gone, but I get the same error from git-cl: [lilypond-git (philomelos %)]$ git-cl upload master No output from [‘git', 'diff', '--no-color', '--no-ext-diff

Re: git-cl problem

mand line? E.g. git --version? > > > > Sent via the Samsung Galaxy S®6 active, an AT 4G LTE smartphone > > > Original message > From: John Gourlay <j...@weathervanefarm.net> > Date: 4/29/2016 6:04 PM (GMT-07:00) > To: LilyPond Developme

RE: git-cl problem

ond-devel@gnu.org> Subject: git-cl problem At long last I’m ready to upload the changes that I’ve been working on (updating musicxml2ly from Philomelos, issue 4751), but git-cl is not working for me. This is what I see in my terminal window: [lilypond-git (philomelos %)]$ git-cl upload master **

git-cl problem

At long last I’m ready to upload the changes that I’ve been working on (updating musicxml2ly from Philomelos, issue 4751), but git-cl is not working for me. This is what I see in my terminal window: [lilypond-git (philomelos %)]$ git-cl upload master ** (emacs:13854): WARNING **: Error

Re: git-cl problem?

James Lowe <p...@gnu.org> writes: > Hello David, > >>File "/usr/local/tmp/git-cl/upload.py", line 1220, in UploadBaseFiles >> print t.get(timeout=60) >>File "/usr/lib/python2.7/multiprocessing/pool.py", line 567, in get >>

Re: git-cl problem?

On 16/04/16 23:24, David Kastrup wrote: 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

git-cl problem?

Hi, I only manage to get dak@lola:/usr/local/tmp/lilypond$ git cl upload lily/context-def.cc | 2 +- lily/include/lily-proto.hh | 1 + lily/include/performer.hh | 1 - lily/include/translator.hh | 67 --- lily

Re: Unable to use git-cl

On 3/8/16 2:40 PM, "Federico Bruni" wrote: >Il giorno mar 8 mar 2016 alle 22:02, Trevor Daniels > ha scritto: >> The SSL error you're seeing has been reported when users upgraded to >> python 2.7.9. Have you perhaps got this or a later version of

Re: Unable to use git-cl

Il giorno mar 8 mar 2016 alle 22:02, Trevor Daniels ha scritto: The SSL error you're seeing has been reported when users upgraded to python 2.7.9. Have you perhaps got this or a later version of python installed? I still have 2.4.5, as distributed with Lily, and it

Re: Unable to use git-cl

Carl, you wrote Tuesday, March 08, 2016 6:54 PM > > I can upload patches to Rietveld, as you can see at > > https://codereview.appspot.com/283550043 > > but the links to the issue tracker never get made. > > As far as I can see, we have a custom git-cl, so I can't get

Re: Unable to use git-cl

On 08.03.2016 19:54, Carl Sorensen wrote: I would hate to leave LilyPond development, but it appears that I have no choice, as I cannot contribute with a broken toolchain. I can upload patches to Rietveld, as you can see at https://codereview.appspot.com/283550043 but the links to the issue

Re: Unable to use git-cl

ed JavaScript in your Web browser? (I was >>> unable to post anything until I complied with SourceForge demanding to >>> execute non-free JavaScript code in my browser.) >>> When issuing git cl upload, does the actual page open in your Web >>> browser? Does it te

Re: Unable to use git-cl

It appears that my ssl certificate is not working properly. Greetings Carl, have you by any chance disabled JavaScript in your Web browser? (I was unable to post anything until I complied with SourceForge demanding to execute non-free JavaScript code in my browser.) When issuing git cl upload, doe

Re: Unable to use git-cl

ertificate is not working properly. > >Greetings Carl, >have you by any chance disabled JavaScript in your Web browser? (I was >unable to post anything until I complied with SourceForge demanding to >execute non-free JavaScript code in my browser.) >When issuing git cl upload, does the act

Re: Unable to use git-cl

demanding to execute non-free JavaScript code in my browser.) When issuing git cl upload, does the actual page open in your Web browser? Does it tell you that everything is ok or does it complain about something? Cheers, Valentin. ___ lilypond-devel mai

Unable to use git-cl

Dear developers, I'm still trying, unsuccessfully, to get git-cl to work on my system. I have done my best to follow the instructions at http://www.lilypond.org/doc/v2.19/Documentation/contributor/git_002dcl#configuring-git_002dcl As far as I can see, everything is fine at SourceForge -- I'm

Re: Difficulty using git-cl upload -- can't update Issue status

- Original Message - From: "Carl Sorensen" <c_soren...@byu.edu> To: "Phil Holmes" <m...@philholmes.net>; "Carl Sorensen" <carl.d.soren...@gmail.com>; <lilypond-devel@gnu.org> Sent: Tuesday, February 16, 2016 12:37 PM Subject: Re

Re: Difficulty using git-cl upload -- can't update Issue status

gt; To: <lilypond-devel@gnu.org> > Sent: Monday, February 15, 2016 9:59 PM > Subject: Difficulty using git-cl upload -- can't update Issue status > > > I just got a new LilyDev setup running so that I can contribute some >> patches again and I got the following me

Re: Difficulty using git-cl upload -- can't update Issue status

On 2/16/16 2:13 AM, "Phil Holmes" <m...@philholmes.net> wrote: >- Original Message - >From: "Carl Sorensen" <carl.d.soren...@gmail.com> >To: <lilypond-devel@gnu.org> >Sent: Monday, February 15, 2016 9:59 PM >Subject: Difficulty usi

Re: Difficulty using git-cl upload -- can't update Issue status

- Original Message - From: "Carl Sorensen" <carl.d.soren...@gmail.com> To: <lilypond-devel@gnu.org> Sent: Monday, February 15, 2016 9:59 PM Subject: Difficulty using git-cl upload -- can't update Issue status I just got a new LilyDev setup running so that I can c

Difficulty using git-cl upload -- can't update Issue status

I just got a new LilyDev setup running so that I can contribute some patches again and I got the following message: Problem setting patch status for Allura issue Is there a configuration change I need to make? THe patch is posted, but it just didn't change the issue to Status:Patch. Thanks,

Re: Doc: CG: Merge and remove redundant git-cl info (issue 285350043 by paulwmor...@gmail.com)

On 2016/02/03 04:27:15, pwm wrote: Please review, thanks, -Paul These changes look fine to me. John Gourlay https://codereview.appspot.com/285350043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org

Doc: CG: Merge and remove redundant git-cl info (issue 285350043 by paulwmor...@gmail.com)

Reviewers: , Message: Please review, thanks, -Paul Description: Doc: CG: Merge and remove redundant git-cl info Please review this at https://codereview.appspot.com/285350043/ Affected files (+43, -114 lines): M Documentation/contributor/quick-start.itexi M Documentation/contributor

Re: git-cl documentation and issue #4666

Hello Paul On 19/01/16 21:57, Paul Morris wrote: > Hi James, > > I thought your CG edits in issue 4666 were a really helpful improvement: > https://sourceforge.net/p/testlilyissues/issues/4666/ Thanks, > > Did you intend to keep this git-cl info (install and configuration) in &

Re: git-cl documentation and issue #4666

> On Jan 21, 2016, at 12:03 PM, James wrote: > > This checkin was a very large edit, and I in these cases I am careful > (hopefully) to *not* remove information from other sections at least at > first, but mainly because my intention was to try to consolidate some of > these

git-cl documentation and issue #4666

Hi James, I thought your CG edits in issue 4666 were a really helpful improvement: https://sourceforge.net/p/testlilyissues/issues/4666/ Did you intend to keep this git-cl info (install and configuration) in the 3.3.4 Commits and Patches section, so that it is repeated in both places? Seems

Re: Change several instances of "git cl" in the Contributors Guide to "git-cl". (issue 282960043 by j...@weathervanefarm.net)

> On Jan 9, 2016, at 9:45 AM, John Gourlay <j...@weathervanefarm.net> wrote: > > I made the changes to create more consistency in the documentation. The > Contributor’s Guide sometimes said “git cl” and sometimes said “git-cl”. > Being new to LilyPond development and needin

Re: Change several instances of "git cl" in the Contributors Guide to "git-cl". (issue 282960043 by j...@weathervanefarm.net)

Is this needed in some environments/with some git versions? git cl with a space always worked for me (just as all the regular git commands did). It doesn't hurt though, so LGTM. https://codereview.appspot.com/282960043/ ___ lilypond-devel mailing

Re: Change several instances of "git cl" in the Contributors Guide to "git-cl". (issue 282960043 by j...@weathervanefarm.net)

Benko, I made the changes to create more consistency in the documentation. The Contributor’s Guide sometimes said “git cl” and sometimes said “git-cl”. Being new to LilyPond development and needing to learn how git-cl works, I found it confusing that there were two different ways of talking

Re: Error in git-cl creating a new issue

2016-01-06 4:07 GMT+01:00 John Gourlay <j...@weathervanefarm.net>: > 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 f

Re: Error in git-cl creating a new issue

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

On 06.01.2016 12:48, Thomas Morley wrote: 2016-01-06 4:07 GMT+01:00 John Gourlay <j...@weathervanefarm.net>: 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

Re: Error in git-cl creating a new issue

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 &

Re: Error in git-cl creating a new issue

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 us

Re: Error in git-cl creating a new issue

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

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

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

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

Error in git-cl creating a new issue

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 why

Re: git cl problem: Couldn’t create Allura issue

- Original Message - From: "Simon Albrecht" <simon.albre...@mail.de> To: "Phil Holmes" <m...@philholmes.net>; "ly-devel" <lilypond-devel@gnu.org> Sent: Tuesday, December 29, 2015 4:19 PM Subject: Re: git cl problem: Couldn’t create Allur

Re: git cl problem: Couldn’t create Allura issue

On 29.12.2015 15:38, Phil Holmes wrote: - Original Message - From: "Simon Albrecht" <simon.albre...@mail.de> To: "ly-devel" <lilypond-devel@gnu.org> Sent: Monday, December 28, 2015 10:12 PM Subject: git cl problem: Couldn’t create Allura issue Hello

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 <simon.albre...@mail.de>: 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

Re: git cl problem: Couldn’t create Allura issue

- Original Message - From: "Simon Albrecht" <simon.albre...@mail.de> To: "ly-devel" <lilypond-devel@gnu.org> 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 al

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

Re: git cl issue: Changing Allura patch status for updated patch set

- Original Message - From: "Simon Albrecht" <simon.albre...@mail.de> To: "ly-devel" <lilypond-devel@gnu.org> Sent: Wednesday, December 23, 2015 11:52 PM Subject: git cl issue: Changing Allura patch status for updated patch set (putting this into an

Re: git cl issue: Changing Allura patch status for updated patch set

Phil, On 24/12/15 09:24, Phil Holmes wrote: > - Original Message - From: "Simon Albrecht" > <simon.albre...@mail.de> > To: "ly-devel" <lilypond-devel@gnu.org> > Sent: Wednesday, December 23, 2015 11:52 PM > Subject: git cl issue: Cha

git cl issue: Changing Allura patch status for updated patch set

(putting this into an extra e-mail) Hello Phil, when uploading a new version of a patch set already on Rietveld, git cl sports an error message about how it couldn’t update the Patch status on Allura. Can you fix this? Thanks for providing the tool! Simon

Re: git cl wording issue

- Original Message - From: "Urs Liska" <u...@openlilylib.org> To: "lilypond-devel" <lilypond-devel@gnu.org> Sent: Monday, December 21, 2015 11:16 PM Subject: git cl wording issue Just used the current git-cl for the first time and noticed a *minor* g

Re: Two git-cl questions

- Original Message - From: "Simon Albrecht" <simon.albre...@mail.de> To: "ly-devel" <lilypond-devel@gnu.org> Sent: Monday, December 21, 2015 7:14 PM Subject: Two git-cl questions Hello, after a long time I’ve now tried and uploaded a patch again. Two

Re: Two git-cl questions

2015-12-21 20:14 GMT+01:00 Simon Albrecht <simon.albre...@mail.de>: > Hello, > > after a long time I’ve now tried and uploaded a patch again. Two questions > on the git cl process: > What exact value should I use for ‘Allura server’? I didn’t get that right. git con

Re: Two git-cl questions

The editor that is opened depends on the EDITOR environment variable so you can use whatever you want. HTH Urs Am 21. Dezember 2015 20:14:57 MEZ, schrieb Simon Albrecht <simon.albre...@mail.de>: >Hello, > >after a long time I’ve now tried and uploaded a patch again. Two >qu

Re: Two git-cl questions

On 21.12.2015 22:09, Phil Holmes wrote: - Original Message - From: "Simon Albrecht" <simon.albre...@mail.de> To: "ly-devel" <lilypond-devel@gnu.org> Sent: Monday, December 21, 2015 7:14 PM Subject: Two git-cl questions Hello, after a long time I’v

Re: Two git-cl questions

On 21.12.2015 22:17, Thomas Morley wrote: 2015-12-21 20:14 GMT+01:00 Simon Albrecht <simon.albre...@mail.de>: Hello, after a long time I’ve now tried and uploaded a patch again. Two questions on the git cl process: What exact value should I use for ‘Allura server’? I didn’t get that

Two git-cl questions

Hello, after a long time I’ve now tried and uploaded a patch again. Two questions on the git cl process: What exact value should I use for ‘Allura server’? I didn’t get that right. And, please, is there a way to upload a patch and edit the message without vi? I have absolutely no experience

git cl wording issue

Just used the current git-cl for the first time and noticed a *minor* glitch. This link in the console output: Ticket created at: https://sourceforge.net/rest/p/testlilyissues/issues/4704/ points to the raw (JSON?) data. In order to provide a useful clickable link the "rest/&qu

git-cl

An updated version is now available. This should fix a variety of bugs associated with git cl status, including the one David K reported. If anyone does find a bug with git cl, please report it to this list with a heading of something like 'git cl bug'. That way I won't lose

  1   2   3   4   >