public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: Modi Mo <modimo@microsoft.com>, "law@redhat.com" <law@redhat.com>,
	 Nicholas Krause <xerofoify@gmail.com>,
	Eric Gallager <egall@gwmail.gwu.edu>,
	Pedro Alves <pedro@palves.net>
Cc: Gabriel Dos Reis <gdr@microsoft.com>,
	Andrew Dean <Andrew.Dean@microsoft.com>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
	 "ro@CeBiTec.Uni-Bielefeld.DE" <ro@cebitec.uni-bielefeld.de>,
	"mikestump@comcast.net" <mikestump@comcast.net>,
	 "jason@redhat.com" <jason@redhat.com>,
	Jonathan Wakely <cxx@kayari.org>,
	Richard Biener <richard.guenther@gmail.com>
Subject: Re: [EXTERNAL] Re: GCC selftest improvements
Date: Tue, 25 Feb 2020 22:11:00 -0000	[thread overview]
Message-ID: <55b69c47cdf69bc8ace1cf0547468735836c5ec1.camel@redhat.com> (raw)
In-Reply-To: <BY5PR21MB150856648E5AE6CBEAA4B472CCED0@BY5PR21MB1508.namprd21.prod.outlook.com>

On Tue, 2020-02-25 at 19:58 +0000, Modi Mo wrote:
> > On 2/12/20 8:53 PM, David Malcolm wrote:
> > The patch will need an update to the docs; search for
> > "Tools/packages necessary for building GCC" in
> > gcc/doc/install.texi, which currently has some paragraphs labelled:
> >    @item ISO C++98 compiler
> > that will need changing.
> 
> Added this change in the attached patch.

Thanks Modi.

Before looking at the updated patch in detail, we ought to also address
the legal prerequisites for contributing.

Does your employer have legal paperwork in place with the FSF for such
contributions?  See:
  https://gcc.gnu.org/contribute.html#legal

I'm not sure what the threshold is for a contribution to be regarded as
"significant", but it seems that we ought to be fastidious here, given
historical attitudes between Microsoft and the FLOSS community.

(I'm not speaking on behalf of anyone other than myself here, as a GCC
maintainer, and I don't mean for this to come across as personal)

Thanks
Dave

  reply	other threads:[~2020-02-25 22:11 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 20:50 Andrew Dean via gcc
2019-10-24 21:09 ` Jonathan Wakely
2019-10-25  6:17 ` David Malcolm
2019-10-25 22:38   ` Andrew Dean via gcc
2019-10-26  0:01     ` Gabriel Dos Reis via gcc
2019-10-26 22:46       ` Eric Gallager
2019-10-31 15:56         ` Pedro Alves
2019-12-02  2:50           ` Eric Gallager
2020-02-13  0:49             ` [EXTERNAL] " Modi Mo via gcc
2020-02-13  1:53               ` David Malcolm
2020-02-13  2:28                 ` Nicholas Krause
2020-02-13 22:18                   ` Modi Mo via gcc
2020-02-14 14:55                     ` C++11 bootstrap (was: GCC selftest improvements) Jason Merrill
2020-02-14 23:10                     ` [EXTERNAL] Re: GCC selftest improvements Segher Boessenkool
2020-02-15 16:14                     ` Jeff Law
2020-02-25 19:58                       ` Modi Mo via gcc
2020-02-25 22:11                         ` David Malcolm [this message]
2020-02-25 22:13                           ` Gabriel Dos Reis via gcc
2020-03-02 22:19                           ` Modi Mo via gcc
2019-10-28 19:40       ` Jeff Law
2019-10-28 19:42         ` Richard Biener
2019-10-28 19:44           ` Jeff Law
2019-10-28 19:46             ` Gabriel Dos Reis via gcc
2019-10-28 20:27         ` Segher Boessenkool
2019-10-28 21:41           ` Jeff Law
2019-10-28 21:47             ` Jakub Jelinek
2019-10-28 21:52               ` Andrew Pinski
2019-10-28 22:02                 ` Jeff Law
2019-10-28 22:03                 ` Gabriel Dos Reis via gcc
2019-10-29  8:41               ` Richard Biener
2019-10-31 16:09                 ` Pedro Alves
2019-10-28 21:50             ` Iain Sandoe
2019-10-28 22:12             ` Segher Boessenkool
2019-10-29  8:45               ` Richard Biener
2019-11-22 21:02                 ` Andrew Dean via gcc
2019-11-22 22:02                   ` Segher Boessenkool
2019-11-22 22:36                     ` Jakub Jelinek
2019-11-22 23:41                       ` Segher Boessenkool
2019-11-23 16:33                         ` Jeff Law
2019-11-23 23:03                           ` Nicholas Krause
2020-02-14 20:50         ` Mike Stump

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=55b69c47cdf69bc8ace1cf0547468735836c5ec1.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=Andrew.Dean@microsoft.com \
    --cc=cxx@kayari.org \
    --cc=egall@gwmail.gwu.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=gdr@microsoft.com \
    --cc=jason@redhat.com \
    --cc=law@redhat.com \
    --cc=mikestump@comcast.net \
    --cc=modimo@microsoft.com \
    --cc=pedro@palves.net \
    --cc=richard.guenther@gmail.com \
    --cc=ro@cebitec.uni-bielefeld.de \
    --cc=xerofoify@gmail.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).