Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org
Subject: Re: Update some sim copyright headers to GPLv3-or-later
Date: Thu, 20 Dec 2012 03:58:00 -0000	[thread overview]
Message-ID: <20121220035750.GC6130@adacore.com> (raw)
In-Reply-To: <201212191353.49689.vapier@gentoo.org>

Mike,

Thanks for looking at the patch :).

> 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.

> 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?

> for the others, i'm guessing this was a script based conversion ?  i'm
> not sure this can be blindly done as someone has to double check there
> aren't any GPLv2 specific files.  unlikely, and probably already
> problematic if such an issue exists, but still better to verify first
> ...

Yes, it was a script based conversion (or rather, perl one-liners).
But I used a regexp that verified that we had the option of switching
to a later version of the GPL. I scanned a large number of the changes,
but I did not check each one of them individually.

-- 
Joel


  reply	other threads:[~2012-12-20  3:58 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 [this message]
2012-12-20  4:20     ` Joel Brobecker
2012-12-20  4:34     ` Mike Frysinger
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=20121220035750.GC6130@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=vapier@gentoo.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