public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Bernardo Innocenti <bernie@develer.com>
To: overseers@sources.redhat.com
Subject: Fwd: CVS write access
Date: Wed, 20 Aug 2003 17:28:00 -0000	[thread overview]
Message-ID: <200308201928.34874.bernie@develer.com> (raw)

Hello,

David Edelsohn suggested me to forward my request here:


----------  Forwarded Message  ----------

Subject: CVS write access
Date: Wednesday 20 August 2003 19:14
From: Bernardo Innocenti <bernie@develer.com>
To: gcc@gcc.gnu.org
Cc: Richard Henderson <rth@redhat.com>, sourcemaster@sources.redhat.com

Hello,

I have a few approved m68k patches still not committed and several
more still pending submission.

On August 14, I've applied for CVS write access using the web form on
sources.redhat.com, and I've still got no confirmation.

Since September, I'll be buried with my regular work and unable to
contribute much to GCC. I still hope to be able to merge-in all the bits
required to properly support ColdFire and uClinux targets in time for
the 3.4 release.

Richard, if it turns out to take much more time, would you mind
committing those patches for me? I could post the complete list sorted
by dependency.

--
  // Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/  http://www.develer.com/

Please don't send Word attachments -
 http://www.gnu.org/philosophy/no-word-attachments.html

-------------------------------------------------------

-- 
  // Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/  http://www.develer.com/

Please don't send Word attachments - http://www.gnu.org/philosophy/no-word-attachments.html


             reply	other threads:[~2003-08-20 17:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-20 17:28 Bernardo Innocenti [this message]
2003-08-20 17:41 ` Christopher Faylor
2003-08-20 18:05   ` Bernardo Innocenti
2003-08-20 18:12     ` Christopher Faylor
2003-08-20 18:22       ` Bernardo Innocenti
2003-08-20 18:34       ` Per Bothner

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=200308201928.34874.bernie@develer.com \
    --to=bernie@develer.com \
    --cc=overseers@sources.redhat.com \
    /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).