* Requesting git write access
@ 2016-02-11 22:59 Andrew Pinski
2016-03-04 19:56 ` Roland McGrath
0 siblings, 1 reply; 2+ messages in thread
From: Andrew Pinski @ 2016-02-11 22:59 UTC (permalink / raw)
To: GNU C Library
Hi,
I know this is not the normal procedure to give out glibc git access
to people who have not contributed any patches yet but I thought I
would l ask anyways. I want to create a branch in the glibc repo so
the aarch64 ilp32 changes could live there so other folks in the
AARCH64 community can help out. Also I have a few more glibc patches
for AARCH64 that I would like to live in the same repo too. I am a
trusted developer for both gcc and binutils/gdb already.
I also want to maintain Cavium's glibc source on the repo as a vendor
branch also.
Thanks,
Andrew Pinski
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Requesting git write access
2016-02-11 22:59 Requesting git write access Andrew Pinski
@ 2016-03-04 19:56 ` Roland McGrath
0 siblings, 0 replies; 2+ messages in thread
From: Roland McGrath @ 2016-03-04 19:56 UTC (permalink / raw)
To: Andrew Pinski; +Cc: GNU C Library
I think you are a sufficiently known quantity that it's certainly fine.
Really the primary requirement is that we all trust you (in integrity,
judgment, and competence) to obey the project's conventions about making
changes to the repo. We definitely want to encourage anybody doing any
serious glibc work to share their branches.
Just send a request to overseers with me CC'd and I'll approve.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-03-04 19:56 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-02-11 22:59 Requesting git write access Andrew Pinski
2016-03-04 19:56 ` Roland McGrath
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).