From: Alan Modra <amodra@gmail.com>
To: binutils@sourceware.org
Cc: gdb-patches@sourceware.org, gcc-patches@gcc.gnu.org
Subject: copyright dates in binutils (and includes/)
Date: Thu, 27 Feb 2014 04:50:00 -0000 [thread overview]
Message-ID: <20140227045011.GC14922@bubble.grove.modra.org> (raw)
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 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
- 2003, 2004, 2005, 2006, 2007, 2010, 2011
- Free Software Foundation, Inc.
+ Copyright (C) 1993-2014 Free Software Foundation, Inc.
This file is part of BFD, the Binary File Descriptor library.
Does anyone have a violent objection to committing updates in
bfd, binutils, elfcpp, gas, gold, gprof, ld, and opcodes?
How about includes/ too? The choices there are
a) apply to just binutils owned files,
b) apply to binutils+gdb files,
c) apply to the lot, and update gcc/include/ too.
I see Joel already updated include/gdb, but the script makes a further
small change. So choice (b) in include/gdb consists of patches like
the following:
diff --git a/include/gdb/gdb-index.h b/include/gdb/gdb-index.h
index d846b04..a8d4f2f 100644
--- a/include/gdb/gdb-index.h
+++ b/include/gdb/gdb-index.h
@@ -1,5 +1,5 @@
/* Public attributes of the .gdb_index section.
- Copyright 2012-2014 Free Software Foundation, Inc.
+ Copyright (C) 2012-2014 Free Software Foundation, Inc.
This file is part of GDB.
--
Alan Modra
Australia Development Lab, IBM
next reply other threads:[~2014-02-27 4:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 4:50 Alan Modra [this message]
2014-02-27 13:25 ` Joel Brobecker
2014-02-27 18:47 ` Joseph S. Myers
2014-02-28 8:57 ` Alan Modra
2014-02-28 13:08 ` Joel Brobecker
2014-02-28 18:22 ` Joseph S. Myers
2014-03-03 3:45 ` Alan Modra
2014-03-03 4:16 ` Alan Modra
2014-03-03 13:33 ` Richard Sandiford
2014-03-05 12:34 ` Alan Modra
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=20140227045011.GC14922@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--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