From: Alan Modra <amodra@gmail.com>
To: binutils@sourceware.org, gdb-patches@sourceware.org,
gcc-patches@gcc.gnu.org, rsandifo@linux.vnet.ibm.com
Subject: Re: copyright dates in binutils (and includes/)
Date: Wed, 05 Mar 2014 12:34:00 -0000 [thread overview]
Message-ID: <20140305123359.GI26922@bubble.grove.modra.org> (raw)
In-Reply-To: <877g8bxv8h.fsf@sandifor-thinkpad.stglab.manchester.uk.ibm.com>
On Mon, Mar 03, 2014 at 01:33:18PM +0000, Richard Sandiford wrote:
> Alan Modra <amodra@gmail.com> 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 makes sense.
I guess we have 8 months to decide what to do with my hacks. :-) If
you choose to merge my changes that's fine by me too.
> As far as including include/ goes: the only reason that didn't happen
> for gcc/ was because I didn't want to sort out which files were GCC-
> specific and whether binutils, GCC or GDB was the master for each file.
> So if we do your option (b) I think we should do (c) as well. I suppose
> that means syncing GCC's include/ with binutils+gdb and then adding
> GCC's include/ to the list of "approved" directories. I'm happy to try
> that if it sounds OK. (Maybe after the 4.9 release, not sure.)
I'm happy with (c, but for now have committed just the other changes.
--
Alan Modra
Australia Development Lab, IBM
prev parent reply other threads:[~2014-03-05 12:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 4:50 Alan Modra
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 [this message]
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=20140305123359.GI26922@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=rsandifo@linux.vnet.ibm.com \
/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