From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: copyright years updated on 7.4 branch
Date: Fri, 06 Jan 2012 04:48:00 -0000 [thread overview]
Message-ID: <1325825242-14383-1-git-send-email-brobecker@adacore.com> (raw)
Hello,
I realized yesterday evening that gdb-7.4 should at least say
2012 in the version output (same for GDBserver), so I imported
that patch. And then, thinking it over, I just thought that
it would be simpler for everyone if I also udpated the copyright
notices everywhere. So I ended up importing the following
changes from HEAD...
(1/5) gdb/gdbserver/gdbreplay: Update copyright year in version out
(2/5) Update the copyright header of various files...
(3/5) more copyright notice reformatting.
(4/5) [README] Add note about copyright and license notices
... and then re-running HEAD's copyright.py on the 7.4 checkout.
This is:
(5/5) Copyright year update in most files of the GDB Project.
The last patch was inspected visually again, checking changes
for each file extension separately. And the whole patch series
was also tested on x86_64-linux.
As the time of this writing, the "cvs ci" is still going, but
should terminate soon.
next reply other threads:[~2012-01-06 4:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 4:48 Joel Brobecker [this message]
2012-01-06 4:48 ` [7.4/commit 1/5] gdb/gdbserver/gdbreplay: Update copyright year in version out Joel Brobecker
2012-01-06 4:49 ` [7.4/commit 4/5] [README] Add note about copyright and license notices Joel Brobecker
2012-01-06 4:49 ` [7.4/commit 2/5] Update the copyright header of various files Joel Brobecker
2012-01-06 4:49 ` [7.4/commit 3/5] more copyright notice reformatting Joel Brobecker
2012-01-06 4:50 ` [7.4/commit 5/5] Copyright year update in most files of the GDB Project Joel Brobecker
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=1325825242-14383-1-git-send-email-brobecker@adacore.com \
--to=brobecker@adacore.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).