public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
* Request write access to GCC
@ 2015-05-15 21:04 James Bowman
  2015-05-16  4:35 ` Ian Lance Taylor
  0 siblings, 1 reply; 6+ messages in thread
From: James Bowman @ 2015-05-15 21:04 UTC (permalink / raw)
  To: overseers; +Cc: Jeff Law

Hello,

I have an existing account

jamesbowman@sourceware.org

And I am requesting "write after approval" access to the GCC project. My sponsor is
Jeff Law [law@redhat.com]

Thanks very much.

--
James Bowman
FTDI Open Source Liaison

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Request write access to GCC
  2015-05-15 21:04 Request write access to GCC James Bowman
@ 2015-05-16  4:35 ` Ian Lance Taylor
  0 siblings, 0 replies; 6+ messages in thread
From: Ian Lance Taylor @ 2015-05-16  4:35 UTC (permalink / raw)
  To: James Bowman; +Cc: overseers, Jeff Law

James Bowman <james.bowman@ftdichip.com> writes:

> I have an existing account
>
> jamesbowman@sourceware.org
>
> And I am requesting "write after approval" access to the GCC
> project. My sponsor is
> Jeff Law [law@redhat.com]

Done.

Ian

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Request write access to gcc
  2009-12-07 11:02   ` Shujing Zhao
@ 2009-12-07 18:34     ` Ian Lance Taylor
  0 siblings, 0 replies; 6+ messages in thread
From: Ian Lance Taylor @ 2009-12-07 18:34 UTC (permalink / raw)
  To: Shujing Zhao; +Cc: overseers

Shujing Zhao <pearly.zhao@oracle.com> writes:

> On 12/04/2009 01:50 PM, Ian Lance Taylor wrote:
>>
>> I have replaced your old SSH key with the one you sent, and added you to
>> the gcc group.
>>
> I'm very sorry to cause you this trouble again.
> I have messed the public and write-enabled trees and got in trouble
> with commit. The old private key is cover incautiously when I try to
> solve the commit problem.
> Can you replace my old SSH key with this one again?

Done.

Ian

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Request write access to gcc
  2009-12-04  5:51 ` Ian Lance Taylor
@ 2009-12-07 11:02   ` Shujing Zhao
  2009-12-07 18:34     ` Ian Lance Taylor
  0 siblings, 1 reply; 6+ messages in thread
From: Shujing Zhao @ 2009-12-07 11:02 UTC (permalink / raw)
  To: overseers; +Cc: Ian Lance Taylor

On 12/04/2009 01:50 PM, Ian Lance Taylor wrote:
> 
> I have replaced your old SSH key with the one you sent, and added you to
> the gcc group.
> 
I'm very sorry to cause you this trouble again.
I have messed the public and write-enabled trees and got in trouble with commit. 
  The old private key is cover incautiously when I try to solve the commit problem.
Can you replace my old SSH key with this one again?
ssh-dss 
AAAAB3NzaC1kc3MAAACBAPV14UHFwNa4QpTM+PMsEMFrTSkpZMg9ILqf6sAMSJrfgOs9oMfeGknL96K3aYMQMlq5/akf5IwpkWWLPMG5ikvPkPZjJFqo3LaJnxI/LCmfkWHUl1gZGtSlwrmgcCwwAvICOfPLC0RxbQL48LDZuTLLaUtmmWrXdTGg+jsI6N+1AAAAFQCSnWsEPZKwWtScx2NMAF0EILDbvQAAAIEAhPJKVXoy7MrBCmGMWV6ciTjOfOeHc398wkq7wV8vRbwW54qXUKc3lgv7yZGo2lb48n+ryvmxYuqtvOsQOR/8ul1iFgnxv5JjQNqTyOWG1SR2qvsVzDdxj1j2dVA58PczSdu+IfXhcYYdHtNl1A5GQPkwCNxmPBQ4KZirfCEmN90AAACBAOEIVnD/7ieu8nLkvLFiU1U8Z4tzxFYOzN5qFs4ZUkMj+N7NuyowTpAOjRJqzXiTaERqmXYwL36H2l1Sl1aliZ8mw9x8l+lPfi1U6BGg++F47h7V/rqMITlmjn3OP9BKvRXdZvhEkLpHxkp0cLaebKbQL6vvnJcgKst3RhX5CJv+ 
pzhao@zhao

Sorry
Pearly

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Request write access to gcc
  2009-12-04  1:49 Request write access to gcc Shujing Zhao
@ 2009-12-04  5:51 ` Ian Lance Taylor
  2009-12-07 11:02   ` Shujing Zhao
  0 siblings, 1 reply; 6+ messages in thread
From: Ian Lance Taylor @ 2009-12-04  5:51 UTC (permalink / raw)
  To: Shujing Zhao; +Cc: overseers

Shujing Zhao <pearly.zhao@oracle.com> writes:

> I have had a sourceware account pzhao@sourceware.org, but it didn't be
> used for a long time. Now I want write access to gcc. Ian Lance Taylor
> <iant@google.com> and Paolo Carlini <paolo.carlini@oracle.com>
> approved me.
> The problem is I have no ssh key at my current pc. I generate a new
> one by "ssh-keygen -t dsa". The contents of .ssh/id_dsa.pub is as the
> following, but I don't know if it is useful.

I have replaced your old SSH key with the one you sent, and added you to
the gcc group.

Ian

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Request write access to gcc
@ 2009-12-04  1:49 Shujing Zhao
  2009-12-04  5:51 ` Ian Lance Taylor
  0 siblings, 1 reply; 6+ messages in thread
From: Shujing Zhao @ 2009-12-04  1:49 UTC (permalink / raw)
  To: overseers

hi,
I have had a sourceware account pzhao@sourceware.org, but it didn't be used for 
a long time. Now I want write access to gcc. Ian Lance Taylor  <iant@google.com> 
and Paolo Carlini <paolo.carlini@oracle.com> approved me.
The problem is I have no ssh key at my current pc. I generate a new one by 
"ssh-keygen -t dsa". The contents of .ssh/id_dsa.pub is as the following, but I 
don't know if it is useful.

ssh-dss 
AAAAB3NzaC1kc3MAAACBAJE0m301vbSW1udaLFHT4zg8hwHKBvrPX6yyCgFQLI4izxLFbQjWr55Vw31sbf+urA9we1XaKkO5CAHLBjdsxegfzyqcYl7nPBWHTc6tO6o4tX5vRnWWLscaeRPEQnqEWhMzEbLNSbdSYCkKwiWQPs4QNU31Sb1aTg6xagq4NkOzAAAAFQDuEMuu458NC/rLz2gvyXS0qU5wjwAAAIBnQ1V1fDIL/bb2JcN51swJoG/oSLgCFLSv5pf/LjKBOe00V+R1NYxOVHs4LmpBc0uwKEtVRz60w2Mlqz9s8OGXm0MMXh5uO6C5JKd/WJb32ymukphd7JgKnmuyH0tm7MZi+QN8Bpn9qLBStB1BCVA0qwK3aGXh99avOiGxKmj5YQAAAIBPNJiRfLG8cX5srryMTOQT7H34bWlRBemDjo4kKoRVPkkxSXf5dHhsTDvbIlx3RdydrzSK7Zz8Jy5RlgAzhOH6ICuzWFZ0cQmiMJNoceRC0RTDb3cDm5W9ZlRBt/IJKwfn8HATflUdbH0cWxCmRUTgzbI9w9cGsKg5c4cyIHKizA== 
pzhao@zhao


Thanks
Pearly

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2015-05-16  4:35 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-05-15 21:04 Request write access to GCC James Bowman
2015-05-16  4:35 ` Ian Lance Taylor
  -- strict thread matches above, loose matches on Subject: below --
2009-12-04  1:49 Request write access to gcc Shujing Zhao
2009-12-04  5:51 ` Ian Lance Taylor
2009-12-07 11:02   ` Shujing Zhao
2009-12-07 18:34     ` Ian Lance Taylor

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).