Colin Campbell writes:
> On 12-07-27 10:25 PM, Werner LEMBERG wrote:
>>> It did not accept your key. Sure you uploaded the _public_ key to
>>> Savannah and it got accepted?
>> Be careful of newlines accidentally inserted in the public key while
>> entering it in the web interface!
>>
>>
>>
Am 27.07.2012 21:14, schrieb Trevor Daniels:
Marc
If git push is still not working one thing to check is how you copied your
public key to Savannah. It must contain no embedded newlines, so you need to
display it using a program that doesn't word-wrap.
If that's not the problem try generatin
>> Be careful of newlines accidentally inserted in the public key
>> while entering it in the web interface!
>
> Opening the key file with Firefox is pretty reliable, IME, as FF
> doesn't break lines.
Good to know. My reason for writing was that I've experienced exactly
this problem, and others
On 12-07-27 10:25 PM, Werner LEMBERG wrote:
It did not accept your key. Sure you uploaded the _public_ key to
Savannah and it got accepted?
Be careful of newlines accidentally inserted in the public key while
entering it in the web interface!
Werner
Opening the key file with Firefox
> It did not accept your key. Sure you uploaded the _public_ key to
> Savannah and it got accepted?
Be careful of newlines accidentally inserted in the public key while
entering it in the web interface!
Werner
___
lilypond-devel mailing list
lil
Marc
If git push is still not working one thing to check is how you copied your
public key to Savannah. It must contain no embedded newlines, so you need to
display it using a program that doesn't word-wrap.
If that's not the problem try generating another key. I think many of us had
to do t
Marc Hohl writes:
> Am 27.07.2012 12:35, schrieb David Kastrup:
>> David Kastrup writes:
>>
>>> Try calling
>>>
>>> ssh -v -v @git.sv.gnu.org/srv/git/lilypond
>>>
>>> This won't ever get you in (because you are not allowed to execute a
>>> normal shell), but it should fail in more informative wa
Am 27.07.2012 12:35, schrieb David Kastrup:
David Kastrup writes:
Try calling
ssh -v -v @git.sv.gnu.org/srv/git/lilypond
This won't ever get you in (because you are not allowed to execute a
normal shell), but it should fail in more informative ways.
Oops. Of course just
ssh -v -v @git.sv.
David Kastrup writes:
> Try calling
>
> ssh -v -v @git.sv.gnu.org/srv/git/lilypond
>
> This won't ever get you in (because you are not allowed to execute a
> normal shell), but it should fail in more informative ways.
Oops. Of course just
ssh -v -v @git.sv.gnu.org
--
David Kastrup
Am 27.07.2012 12:28, schrieb David Kastrup:
Marc Hohl writes:
After Trevor's mail, I found out that I already *had*
.ssh/config|id_rsa|id_rsa.pub etc.
due to some ssh connections to other servers a friend of mine created for me
(I was sitting next to him, but apparently he can type commands fa
Marc Hohl writes:
> After Trevor's mail, I found out that I already *had*
> .ssh/config|id_rsa|id_rsa.pub etc.
> due to some ssh connections to other servers a friend of mine created for me
> (I was sitting next to him, but apparently he can type commands faster
> than I
> could think, so I didn'
Am 27.07.2012 11:07, schrieb Phil Holmes:
- Original Message - From: "Marc Hohl"
To: "Trevor Daniels"
Cc: "David Kastrup" ;
Sent: Friday, July 27, 2012 8:28 AM
Subject: Re: git push doesn't work
I have saved my public key on savannah, and the inst
- Original Message -
From: "Marc Hohl"
To: "Trevor Daniels"
Cc: "David Kastrup" ;
Sent: Friday, July 27, 2012 8:28 AM
Subject: Re: git push doesn't work
I have saved my public key on savannah, and the instructions say that
it will take some time
Am 27.07.2012 09:16, schrieb Trevor Daniels:
Marc Hohl wrote Friday, July 27, 2012 8:11 AM
I must admit that I am not very familiarwith the whole ssh stuff – is
there anything I can do
to make it work? The git instructions on
http://lilypond.org/doc/v2.15/Documentation/contributor
don't seem
Marc Hohl wrote Friday, July 27, 2012 8:11 AM
> I must admit that I am not very familiarwith the whole ssh stuff – is
> there anything I can do
> to make it work? The git instructions on
>
> http://lilypond.org/doc/v2.15/Documentation/contributor
>
> don't seem to cover the ssh protocol in combi
Am 27.07.2012 09:01, schrieb David Kastrup:
Marc Hohl writes:
[remote "origin"]
url = git://git.sv.gnu.org/lilypond.git/
fetch = +refs/heads/master:refs/remotes/origin/master
fetch = +refs/heads/staging:refs/remotes/origin/staging
So I think I am not using http, right?
It is n
Marc Hohl writes:
> [remote "origin"]
> url = git://git.sv.gnu.org/lilypond.git/
> fetch = +refs/heads/master:refs/remotes/origin/master
> fetch = +refs/heads/staging:refs/remotes/origin/staging
>
> So I think I am not using http, right?
It is not an authenticated protocal either, so
Am 27.07.2012 08:45, schrieb David Kastrup:
Marc Hohl writes:
this is the time for my first patch to be pushed by myself ;-)
... and it doesn't work.
I followed the instructions at
http://lilypond.org/doc/v2.15/Documentation/contributor/git-for-the-impatient
My work is on barlineI, so I did
Marc Hohl writes:
> this is the time for my first patch to be pushed by myself ;-)
> ... and it doesn't work.
>
> I followed the instructions at
> http://lilypond.org/doc/v2.15/Documentation/contributor/git-for-the-impatient
>
> My work is on barlineI, so I did
>
> (on master)
>
> git pull
> git
Hi list,
this is the time for my first patch to be pushed by myself ;-)
... and it doesn't work.
I followed the instructions at
http://lilypond.org/doc/v2.15/Documentation/contributor/git-for-the-impatient
My work is on barlineI, so I did
(on master)
git pull
git checkout barlineI
git rebase
20 matches
Mail list logo
