public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gary Funck <gary@intrepid.com>
To: GCC List <gcc@gcc.gnu.org>
Subject: RFC: merging GUPC into the GCC trunk?
Date: Wed, 07 Apr 2010 15:11:00 -0000	[thread overview]
Message-ID: <20100407150514.GC12533@intrepid.com> (raw)

Now that GCC 4.5 has been branched from the main line,
it seems that this is an appropriate time to consider
GUPC for inclusion into the GCC trunk.

GUPC was recently checked in as a GCC branch:
http://gcc.gnu.org/projects/gupc.html

What is the recommended process for having GUPC reviewed
(and hopefully, subsequently approved) for being merged
into the GCC mainline?

Thanks,
- Gary

             reply	other threads:[~2010-04-07 15:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-07 15:11 Gary Funck [this message]
2010-04-07 16:17 ` Diego Novillo
2010-04-24 18:05 ` Gerald Pfeifer

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=20100407150514.GC12533@intrepid.com \
    --to=gary@intrepid.com \
    --cc=gcc@gcc.gnu.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).