On Mon, Mar 03, 2014 at 01:33:18PM +, Richard Sandiford wrote:
> Alan Modra writes:
> > On Mon, Mar 03, 2014 at 02:14:51PM +1030, Alan Modra wrote:
> >> I'll post update-copyright.py separately.
>
> Thanks for doing this, looks good to me FWIW. I don't know whether
> we want to keep a single
Alan Modra writes:
> On Mon, Mar 03, 2014 at 02:14:51PM +1030, Alan Modra wrote:
>> I'll post update-copyright.py separately.
Thanks for doing this, looks good to me FWIW. I don't know whether
we want to keep a single script for both GCC and binutils+gdb or fork,
but probably separate copies mak
On Mon, Mar 03, 2014 at 02:14:51PM +1030, Alan Modra wrote:
> I'll post update-copyright.py separately.
--- /src/gcc-current/contrib/update-copyright.py2013-02-07
12:55:28.272161270 +1030
+++ ./update-copyright.py 2014-03-03 13:44:35.650293322 +1030
@@ -74,6 +74,8 @@
On Fri, 28 Feb 2014, Joel Brobecker wrote:
> > Joseph, do you know why implicitly adding years to the claimed
> > copyright years is a problem? I'm guessing the file needs to be
> > published somewhere for each year claimed.
>
> IANAL, but from 2 discussions with copyright-clerk:
>
> 1. We st
> Joseph, do you know why implicitly adding years to the claimed
> copyright years is a problem? I'm guessing the file needs to be
> published somewhere for each year claimed.
IANAL, but from 2 discussions with copyright-clerk:
1. We start claiming copyright the year the file as committed
On Thu, Feb 27, 2014 at 06:47:17PM +, Joseph S. Myers wrote:
> On Thu, 27 Feb 2014, Joel Brobecker wrote:
>
> > I should mention, however, that for us to use ranges like this,
> > the FSF asked us to add a note explaining that the copyright years
> > could be abbreviated into a range. See gdb/
On Thu, 27 Feb 2014, Joel Brobecker wrote:
> I should mention, however, that for us to use ranges like this,
> the FSF asked us to add a note explaining that the copyright years
> could be abbreviated into a range. See gdb/README (at the end).
> I suspect that you'll need the same note for binutil
Hi Alan,
My two cents...
> --- a/bfd/elf32-sparc.c
> +++ b/bfd/elf32-sparc.c
> @@ -1,7 +1,5 @@
> /* SPARC-specific support for 32-bit ELF
> - Copyright 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
> - 2003, 2004, 2005, 2006, 2007, 2010, 2011
> - Free Software Foundation, Inc
I've been hacking gcc's contrib/update-copyright.py for binutils,
and have run it over binutils to update all the binutils copyright
notices.
Here's an example of the update:
--- a/bfd/elf32-sparc.c
+++ b/bfd/elf32-sparc.c
@@ -1,7 +1,5 @@
/* SPARC-specific support for 32-bit ELF
- Copyright 19
