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
Il giorno ven 27 mag 2016 alle 1:59, John Gourlay
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
wonder if the CG should be revised
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 the
- Original Message -
From: "David Kastrup"
To: "John Gourlay"
Cc: "Phil Holmes" ; "LilyPond Development Team"
Sent: Tuesday, May 03, 2016 4:53 PM
Subject: Re: git-cl problem
John Gourlay writes:
My git-cl seems to be up to date. When I
John Gourlay 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 the symptom appears to be the same whether the issue is
an you
> run git-cl with a new issue?
>
> --
> Phil Holmes
>
>
> - Original Message - From: "John Gourlay"
> To: "Phil Holmes"
> Cc: "LilyPond Development Team"
> Sent: Tuesday, May 03, 2016 2:47 PM
> Subject: Re: git-c
lmes"
Cc: "LilyPond Development Team"
Sent: Tuesday, May 03, 2016 2:47 PM
Subject: Re: git-cl problem
I did go through the steps a couple of months ago to create an Allura bearer
token. Is there some way now to confirm that it’s still valid?
On May 3, 2016, at 4:35 AM, Phil Hol
ment Team"
> 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 use
>> “git-cl upload master”. But, you raise a good point. I have already merged
>>
- Original Message -
From: "John Gourlay"
To: "LilyPond Development Team"
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 use
“git-cl upload master”. But, you raise a good p
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, and this is ev
ctive, an AT&T 4G LTE smartphone
> >
> >
> > Original message
> > From: John Gourlay
> > Date: 4/29/2016 6:04 PM (GMT-07:00)
> > To: LilyPond Development Team
> > Subject: git-cl problem
> >
> > At long last I’
- Original Message -
From: "John Gourlay"
To: "Federico Bruni"
Cc: "LilyPond Development Team"
Sent: Monday, May 02, 2016 3:37 PM
Subject: Re: git-cl problem
Federico,
I am running git-cl in a terminal window. I changed my default editor to
leafpa
version 2.1.4
>>
>> John Gourlay
>>
>>> On Apr 29, 2016, at 8:18 PM, Carl Sorensen wrote:
>>>
>>> Can you run git from the command line? E.g. git --version?
>>>
>>>
>>>
>>> Sent via the Samsung Galaxy S®6 active,
--version?
>
>
>
> Sent via the Samsung Galaxy S®6 active, an AT&T 4G LTE smartphone
>
>
> Original message
> From: John Gourlay
> Date: 4/29/2016 6:04 PM (GMT-07:00)
> To: LilyPond Development Team
> Subject: git-cl problem
>
> At
Can you run git from the command line? E.g. git --version?
Sent via the Samsung Galaxy S®6 active, an AT&T 4G LTE smartphone
Original message
From: John Gourlay
Date: 4/29/2016 6:04 PM (GMT-07:00)
To: LilyPond Development Team
Subject: git-cl problem
At long last
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 retrievi
James Lowe 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
>> raise self._value
>> urllib2.URLError:
>> dak@lola:/usr/local/tmp/lily
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 command
Hello David,
On 16/04/16 23:24, David Kastrup wrote:
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
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/inclu
- 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: &qu
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 ju
- 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 unt
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 thos
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 d
On Tue, Jan 25, 2011 at 08:38:02PM +, James Lowe wrote:
> Jonathan
>
> >Ok I'll add that line. This might be about it before making new .iso
> >file. I've also deleted the pdf CG from desktop already. Graham, do
> >you know of anything else?
Nope, nothing else.
> http://code.google.com/p/lil
Jonathan
-Original Message-
From: Jonathan Kulp
Date: Tue, 25 Jan 2011 13:49:29 -0600
To: "c_soren...@byu.edu"
Cc: lilypond-devel
Subject: Re: Do we have a git-cl problem with lilydev?
>On Tue, Jan 25, 2011 at 1:23 PM, Carl Sorensen wrote:
>>> On Mon, Jan 24,
On Tue, Jan 25, 2011 at 1:23 PM, Carl Sorensen wrote:
>> On Mon, Jan 24, 2011 at 7:03 PM, Carl Sorensen wrote:
>>> We have had multiple contributors (Keith O'Hara, Mike Solomon, Valentin
>>> Villenave) who were unable to successfully upload patches to Rietveld for
>>> review.
>>>
>>> Keith tracke
On 1/25/11 8:44 AM, "Jonathan Kulp" wrote:
> On Mon, Jan 24, 2011 at 7:03 PM, Carl Sorensen wrote:
>> We have had multiple contributors (Keith O'Hara, Mike Solomon, Valentin
>> Villenave) who were unable to successfully upload patches to Rietveld for
>> review.
>>
>> Keith tracked it down to
On Mon, Jan 24, 2011 at 7:03 PM, Carl Sorensen wrote:
> We have had multiple contributors (Keith O'Hara, Mike Solomon, Valentin
> Villenave) who were unable to successfully upload patches to Rietveld for
> review.
>
> Keith tracked it down to a missing entry in /etc/mime.types on his system.
>
Pe
We have had multiple contributors (Keith O'Hara, Mike Solomon, Valentin
Villenave) who were unable to successfully upload patches to Rietveld for
review.
Keith tracked it down to a missing entry in /etc/mime.types on his system.
I've added a note to the CG, so we don't lose Keith's information, b
31 matches
Mail list logo
