From: Diego Novillo <dnovillo@google.com>
To: Gary Funck <gary@intrepid.com>
Cc: GCC List <gcc@gcc.gnu.org>
Subject: Re: RFC: merging GUPC into the GCC trunk?
Date: Wed, 07 Apr 2010 16:17:00 -0000 [thread overview]
Message-ID: <p2yb798aad51004070811rebdd0f8fn901b400fdbd36f58@mail.gmail.com> (raw)
In-Reply-To: <20100407150514.GC12533@intrepid.com>
On Wed, Apr 7, 2010 at 11:05, Gary Funck <gary@intrepid.com> wrote:
> What is the recommended process for having GUPC reviewed
> (and hopefully, subsequently approved) for being merged
> into the GCC mainline?
I would suggest splitting patches across reviewer domains. See
previous merges from big branches for examples. This makes it easier
for maintainers and reviewers to review the relevant parts.
Additionally, make sure that the branch bootstraps and tests on all
primary/secondary platforms with all languages enabled.
I can help reviewing patches in my areas. Please CC me, so it lands
on my Inbox.
Presumably, all the other requirements are met? (copyright paperwork, etc).
Diego.
next prev parent reply other threads:[~2010-04-07 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 15:11 Gary Funck
2010-04-07 16:17 ` Diego Novillo [this message]
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=p2yb798aad51004070811rebdd0f8fn901b400fdbd36f58@mail.gmail.com \
--to=dnovillo@google.com \
--cc=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).