From: Mike Frysinger <vapier@gentoo.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Update some sim copyright headers to GPLv3-or-later
Date: Thu, 20 Dec 2012 04:34:00 -0000 [thread overview]
Message-ID: <201212192334.22589.vapier@gentoo.org> (raw)
In-Reply-To: <20121220035750.GC6130@adacore.com>
[-- Attachment #1: Type: Text/Plain, Size: 1534 bytes --]
On Wednesday 19 December 2012 22:57:50 Joel Brobecker wrote:
> > NAK on sim/bfin/linux-fixed-code.s. that is code coming from the
> > Linux kernel and licensing that under GPLv3 instead of GPLv2 would be
> > entirely pointless (the Linux kernel isn't going GPLv3) and just cause
> > me headaches.
>
> I will revert the change for now, but I will also ask the FSF what
> they want us to do. We were told explicitly that all files that
> were GPLv2 or later should have been switched to GPLv3 or later.
> One tiny change in the copyright header should be manageable, IMO,
> particularly since you're already going to see a yearly change in
> the copyright years as well.
what i mean is worrying about the flow of code. if they aren't both GPLv2
based, i now have to worry about people being able to make the claim that i'm
committing GPLv3 sim code to the GPLv2 kernel and tainting it. considering
the code in question, doing GPLv3 on it will gain nothing.
> > the sim/bfin/aclocal.m4 change doesn't make sense as that is a
> > generated file and it's changing the license on a macro that's been
> > imported from an external project. so it'll just get "reverted" next
> > time the file gets regenerated.
>
> I don't understand exactly the status of this file. Can I just
> regenerate the "reverted" version and the project will still work?
next time someone runs `aclocal` (like me), it'll blow away your changes as it
copies m4 macros from files in /usr/share/ and into the aclocal.m4.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-12-20 4:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 7:26 Joel Brobecker
2012-12-19 8:50 ` Mark Kettenis
2012-12-19 9:05 ` Joel Brobecker
2012-12-19 11:18 ` Mark Kettenis
2012-12-19 11:25 ` Joel Brobecker
2012-12-19 11:38 ` Joel Brobecker
2012-12-20 18:20 ` Alfred M. Szmidt
2012-12-19 18:53 ` Mike Frysinger
2012-12-20 3:58 ` Joel Brobecker
2012-12-20 4:20 ` Joel Brobecker
2012-12-20 4:34 ` Mike Frysinger [this message]
2012-12-20 5:03 ` Joel Brobecker
2012-12-20 22:35 ` Mike Frysinger
2012-12-21 7:44 ` Joel Brobecker
2012-12-21 9:14 ` Eli Zaretskii
2012-12-21 11:38 ` Ralf Corsepius
2012-12-21 12:08 ` Joel Brobecker
2012-12-21 17:30 ` Mike Frysinger
2012-12-21 18:14 ` Joel Brobecker
2012-12-21 18:56 ` Mike Frysinger
2012-12-22 4:43 ` Joel Brobecker
2012-12-24 3:49 ` Mike Frysinger
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=201212192334.22589.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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