From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: Update Copyright and FSF address (was: [RFC] fix testsuite/gdb.cp/printmethod)
Date: Tue, 20 Dec 2005 03:04:00 -0000 [thread overview]
Message-ID: <20051217230610.GA20239@nevyn.them.org> (raw)
In-Reply-To: <u3bkr7353.fsf@gnu.org>
On Sun, Dec 18, 2005 at 12:46:48AM +0200, Eli Zaretskii wrote:
> I've committed the first portion of this monstrous job: all the files
> in gdb/ and in gdb/cli/ now have the (c) marker and state the correct
> FSF address. I hope I didn't break anything, but if I did, please
> correct as obvious.
>
> I don't imagine someone would actually wish to see the humongous
> boring diffs, would they? ;-)
Eli, thank you for doing this. I'll run a couple of test cycles here
to confirm that everything's still in order, but I'm sure it will be
:-)
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-12-17 23:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 22:46 [RFC] fix testsuite/gdb.cp/printmethod Christophe LYON
2005-12-08 9:48 ` Daniel Jacobowitz
2005-12-08 18:37 ` Eli Zaretskii
2005-12-08 19:22 ` Daniel Jacobowitz
2005-12-09 2:12 ` Jim Blandy
2005-12-09 2:25 ` Eli Zaretskii
2005-12-19 22:39 ` Update Copyright and FSF address (was: [RFC] fix testsuite/gdb.cp/printmethod) Eli Zaretskii
2005-12-20 3:04 ` Daniel Jacobowitz [this message]
2005-12-20 14:19 ` Daniel Jacobowitz
2005-12-20 3:18 ` Mark Kettenis
2005-12-24 8:07 ` Eli Zaretskii
2005-12-24 8:57 ` Update Copyright and FSF address Eli Zaretskii
2005-12-24 10:50 ` Update Copyright and FSF address (was: [RFC] fix testsuite/gdb.cp/printmethod) Daniel Jacobowitz
2005-12-24 17:37 ` Eli Zaretskii
2005-12-26 14:39 ` Eli Zaretskii
2005-12-26 19:15 ` Daniel Jacobowitz
2005-12-26 19:31 ` Eli Zaretskii
2005-12-27 4:09 ` Daniel Jacobowitz
2005-12-27 12:23 ` Eli Zaretskii
2005-12-09 8:05 ` [RFC] fix testsuite/gdb.cp/printmethod Mark Kettenis
2005-12-09 18:51 ` Christophe LYON
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=20051217230610.GA20239@nevyn.them.org \
--to=drow@false.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