From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: Revert 2011 copyright year update under gnulib/
Date: Wed, 18 Apr 2012 14:32:00 -0000 [thread overview]
Message-ID: <20120418142453.GZ2852@adacore.com> (raw)
In-Reply-To: <4F8EB031.5070704@redhat.com>
> These are imported sources, so we should keep their copyright years
> intact in the new year procedure. It seems like in 2012 they weren't
> updated, so it looks like the procedure's scripts have been fixed already?
Yes, the new script now avoids updating these files. gdb/copyright.py:
# Files which should not be modified, either because they are
# generated, non-FSF, or otherwise special (e.g. license text,
# or test cases which must be sensitive to line numbering).
#
# Filenames are relative to the root directory.
EXCLUDE_LIST = (
'gdb/gdbarch.c', 'gdb/gdbarch.h',
'gdb/gnulib'
)
That is actually a good reminder that when you are done with your
gnulib modifications, we'll need to adjust the script!
--
Joel
prev parent reply other threads:[~2012-04-18 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 12:34 Pedro Alves
2012-04-18 14:32 ` Joel Brobecker [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=20120418142453.GZ2852@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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