This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Update some sim copyright headers to GPLv3-or-later


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: signature.asc
Description: This is a digitally signed message part.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]