Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org, mec.gnu@mindspring.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfc] Cleanup restore.exp
Date: Fri, 16 Jul 2004 21:11:00 -0000	[thread overview]
Message-ID: <20040716211139.AAECE4B104@berman.michael-chastain.com> (raw)

ac> How about I change it to " caller$c prologue .*" with a corresponding 
ac> tweak to restore.c?  That way there's no confusion.

That would be cool, if you want to do that.

But before you touch restore.c, someone has to add a copyright notice to
it.  restore.c was written by Jim Blandy of Cygnus in 1998 so there's no
doubt that FSF owns it.  It was modified in 1998, 1999, 2001, and 2003
(plus it will be modified in 2004 by adding the notice).

For the record, I got this information from ChangeLog, the cvs
repository, and my set of historical gdb releases.

When adding a copyright notice, one has to test the change, because
some *.exp scripts depend on line numbers in their *.c files.
It appears that restore.exp does not have this problem.

It's enough work that I do "add copyright notice" as a separate patch,
especially because I like to separate legally significant changes
from technically significant changes.

Would you like to add a copyright notice to restore.c, or would you like
me to do it?

Michael C


             reply	other threads:[~2004-07-16 21:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-16 21:11 Michael Elizabeth Chastain [this message]
2004-07-16 21:33 ` Andrew Cagney
2004-07-16 22:22   ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2004-07-16 19:45 Michael Elizabeth Chastain
2004-07-16 20:53 ` Andrew Cagney
2004-07-16 19:27 Andrew Cagney

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=20040716211139.AAECE4B104@berman.michael-chastain.com \
    --to=mec.gnu@mindspring.com \
    --cc=cagney@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