public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Menezes, Evandro" <evandro.menezes@amd.com>
To: "Christopher Faylor" <me@cgf.cx>,
	overseers@sourceware.org, "Meissner,
	Michael" <michael.meissner@amd.com>
Subject: RE: Request from Evandro Menezes
Date: Thu, 13 Apr 2006 21:22:00 -0000	[thread overview]
Message-ID: <84EA05E2CA77634C82730353CBE3A84304940BF0@SAUSEXMB1.amd.com> (raw)

Christopher,

Thanks for the help. 

> -----Original Message-----
> From: Christopher Faylor [mailto:me@cgf.cx] 
> Sent: Thursday, April 13, 2006 14:34
> To: overseers@sourceware.org; Menezes, Evandro; Meissner, Michael
> Subject: Re: Request from Evandro Menezes
> 
> On Thu, Apr 13, 2006 at 02:06:15PM -0500, Menezes, Evandro wrote:
> >Christopher,
> >>Any particular reason why you submitted this request three times?
> >
> >Yes, though perhaps not good ones.  I sent requests for gcc, 
> binutils 
> >and glibc.  If one does it all, my apologies.
> 
> Ah.  That would be sort of implied by the language on the web 
> page which mentions not using the form to submit multiple 
> requests if you already have an account on 
> sourceware.org/gcc.gnu.org since once the first request was 
> handled, you'd have an account on the system.  However, I 
> guess the language should clarify this.
> 
> In any event, I'm pretty certain that Mike doesn't have 
> authority to authorize checkin access to glibc.  You'd need 
> to get permission from Ulrich Drepper or Roland McGrath for that.
> 
> cgf
> 
> 

             reply	other threads:[~2006-04-13 21:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-13 21:22 Menezes, Evandro [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-12-04  7:48 e.menezes
2006-04-13 19:06 Menezes, Evandro
2006-04-13 19:33 ` Christopher Faylor
2006-04-13 14:43 evandro.menezes
2006-04-13 14:43 evandro.menezes
2006-04-13 14:43 evandro.menezes
2006-04-13 16:19 ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=84EA05E2CA77634C82730353CBE3A84304940BF0@SAUSEXMB1.amd.com \
    --to=evandro.menezes@amd.com \
    --cc=me@cgf.cx \
    --cc=michael.meissner@amd.com \
    --cc=overseers@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).