unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: contribution for gud.el
Date: Wed, 26 Feb 2003 04:47:12 -0500	[thread overview]
Message-ID: <E18ny9g-0001RC-00@fencepost.gnu.org> (raw)
In-Reply-To: <20030224020848.C8959@unx.sas.com> (message from Eric Gebhart on Mon, 24 Feb 2003 02:08:49 -0500)

    I've added another debugger to gud.el.  In the process I refined the
    speedbar functionality to make it easier to plug into.  I also added
    functionality for a breaklist.

What is a breaklist?  That is not a term I know.

    I am running emacs 21.2.1 on FreeBSD so I was unable to run the merged version
    of the .el.  No toolbars....

Nick ROberts has made major changes in gud.el to support powerful new
features.  It is possible that some of your changes duplicate some 
of them--I think it is important for you to see if that is true.

    I merged my changes with the current head of gud.el version 1.175.

Thanks--that is important.

Would you please mail us a diff -c showing your changes?
That is what we would like in order to consider them.

Also, I expect your changes are large enough to need legal papers.
Would you be willing to sign a copyright assignment for your changes?

Please email the following information to fsf-records@gnu.org, and we
will send you the assignment form that covers the changes you have
already written.  That form will cover subsequent corrections to those
changes, but it will not cover other unrelated future changes to the
same program.

If you would like to make further contributions to Emacs, and you
would like to avoid the need to sign more papers when you contribute
them, you have another option: to sign a copyright assignment covering
your future changes.  If that is what you want to do, please tell the
maintainer you would prefer to sign an assignment of past and future
changes.
 
Please use your full legal name (in ASCII characters) as the subject line of the message.
---------------------------------------------------------------------
REQUEST:  SEND FORM FOR CHANGES ALREADY MADE

[What is the name of the program or package you're contributing to?]
Emacs

[Did you copy any files or text written by someone else in these changes?
Even if that material is free software, we need to know about it.]


[Do you have an employer who might have a basis to claim to own
your changes?  Do you attend a school which might make such a claim?]


[For the copyright registration, what country are you a citizen of?]


[What year were you born?]


[Please write your email address here.]


[Please write your postal address here.]





[Which files have you changed so far, and which new files have you written
so far?]

           reply	other threads:[~2003-02-26  9:47 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20030224020848.C8959@unx.sas.com>]

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E18ny9g-0001RC-00@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).