public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@google.com>
To: "Paweł Sikora" <pluto@agmk.net>
Cc: gcc@gcc.gnu.org, pedro.lamarao@gmail.com,
	 Ian Lance Taylor <iant@google.com>,
	Lawrence Crowl <crowl@google.com>
Subject: Re: Converting GCC to C++ - new branch cxx-conversion
Date: Wed, 11 Apr 2012 19:48:00 -0000	[thread overview]
Message-ID: <4F85DFF5.5050709@google.com> (raw)
In-Reply-To: <1369197.2kBSDVHZzt@localhost>

On 4/11/12 3:44 PM, Paweł Sikora wrote:

> will this project use (new) gcc mailing list or should we poison ;)
> the core gcc@ list with [cxx-conversion] marker?

This is no different than any other development branch.  We use tagging 
to distinguish patches and messages related to it.


Diego.

      reply	other threads:[~2012-04-11 19:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 16:35 Diego Novillo
2012-04-11 16:41 ` Gabriel Dos Reis
2012-04-11 19:25 ` niXman
2012-04-11 19:44 ` Paweł Sikora
2012-04-11 19:48   ` Diego Novillo [this message]

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=4F85DFF5.5050709@google.com \
    --to=dnovillo@google.com \
    --cc=crowl@google.com \
    --cc=gcc@gcc.gnu.org \
    --cc=iant@google.com \
    --cc=pedro.lamarao@gmail.com \
    --cc=pluto@agmk.net \
    /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).