Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Update Copyright and FSF address (was: [RFC] fix testsuite/gdb.cp/printmethod)
Date: Mon, 19 Dec 2005 22:39:00 -0000	[thread overview]
Message-ID: <u3bkr7353.fsf@gnu.org> (raw)
In-Reply-To: <20051208044236.GB14351@nevyn.them.org> (message from Daniel 	Jacobowitz on Wed, 7 Dec 2005 23:42:36 -0500)

> Date: Wed, 7 Dec 2005 23:42:36 -0500
> From: Daniel Jacobowitz <drow@false.org>
> 
> On Thu, Dec 08, 2005 at 06:38:03AM +0200, Eli Zaretskii wrote:
> > > 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...
> 
> IMO we really should do them all at once.  The other thing we need to
> do is update the FSF address; I have had this flagged to take care of
> since the FSF moved this spring, but I (obviously) haven't found the
> time...

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? ;-)


  parent reply	other threads:[~2005-12-17 22:46 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       ` Eli Zaretskii [this message]
2005-12-20  3:04         ` Update Copyright and FSF address (was: [RFC] fix testsuite/gdb.cp/printmethod) 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     ` [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=u3bkr7353.fsf@gnu.org \
    --to=eliz@gnu.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