From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: eliz@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] fix testsuite/gdb.cp/printmethod
Date: Fri, 09 Dec 2005 08:05:00 -0000 [thread overview]
Message-ID: <200512081938.jB8JcWo0005629@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <u7jagkxuc.fsf@gnu.org> (message from Eli Zaretskii on Thu, 08 Dec 2005 06:38:03 +0200)
> X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on
> elgar.sibelius.xs4all.nl
> X-Spam-Level:
> X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=no
> version=3.1.0
> X-From_: gdb-patches-return-41882-m.m.kettenis=alumnus.utwente.nl@sourceware.org Thu Dec 8 05:38:13 2005
> Date: Thu, 08 Dec 2005 06:38:03 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Reply-to: Eli Zaretskii <eliz@gnu.org>
> X-IsSubscribed: yes
> Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
> Sender: gdb-patches-owner@sourceware.org
> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information.
> X-UTwente-MailScanner: Found to be clean
> X-MailScanner-From: gdb-patches-return-41882-m.m.kettenis=alumnus.utwente.nl@sourceware.org
>
> > Date: Wed, 7 Dec 2005 18:08:07 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: gdb-patches@sources.redhat.com
> >
> > I've checked it in, with some formatting/copyright tweaks
> [...]
> > --- testsuite/gdb.cp/printmethod.cc 17 Jun 2004 18:30:18 -0000 1.2
> > +++ testsuite/gdb.cp/printmethod.cc 7 Dec 2005 23:06:43 -0000
> > @@ -1,6 +1,6 @@
> > /* This test script is part of GDB, the GNU debugger.
> >
> > - Copyright 2002, 2004,
> > + Copyright 2002, 2004, 2005
> > Free Software Foundation, Inc.
>
> According to the copyright notice rules that RMS just published (they
> will probably be available as part of standards.texi or
> maintain.texi), we need to have a "(C)" after the word "Copyright".
> It's true that we don't have this in most of our files, but we might
> as well get started...
Geez, I think we actively removed those in the past at RMS' request.
Well, I suppose it's too much too ask from lawyers too make up their
mind.
Note that we also need to update the FSF address in the copyright
notice.
Mark
next prev parent reply other threads:[~2005-12-08 19:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 22:46 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
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 ` Mark Kettenis [this message]
2005-12-09 18:51 ` [RFC] fix testsuite/gdb.cp/printmethod 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=200512081938.jB8JcWo0005629@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.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