public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Nick Clifton <nickc@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: RFA: GPLv3: gcc/config
Date: Sat, 11 Aug 2007 19:09:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.0708111906030.12511@digraph.polyomino.org.uk> (raw)
In-Reply-To: <m3fy35ipjk.fsf@redhat.com>

On Mon, 30 Jul 2007, Nick Clifton wrote:

> 	arm/predicates.md, arm/iwmmxt.md, arm/arm_neon.h,

arm_neon.h is a generated file, so you need to change the notice that 
neon-gen.ml inserts into its output and regenerate rather than changing 
arm_neon.h on its own manually.

It's also a file including an exception as it's a header to be included in 
user programs, so by my understanding should stay with GPLv2 until we have 
word from the FSF on the correct wording of exceptions to use with GPLv3.

-- 
Joseph S. Myers
joseph@codesourcery.com

  parent reply	other threads:[~2007-08-11 19:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-30 21:05 Nick Clifton
2007-08-02  2:29 ` Mark Mitchell
2007-08-11 19:09 ` Joseph S. Myers [this message]
2007-08-13 10:08   ` Nick Clifton

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=Pine.LNX.4.64.0708111906030.12511@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nickc@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).