From: Richard Stallman <rms@gnu.org>
Cc: nand@mac.com, storm@cua.dk, emacs-devel@gnu.org
Subject: Re: Do we need legal papers
Date: Tue, 04 Nov 2003 09:25:24 -0500 [thread overview]
Message-ID: <E1AH27Y-0007Tc-WE@fencepost.gnu.org> (raw)
In-Reply-To: <m2llqymj3n.fsf@owlbear.local> (message from Andrew Choi on Sun, 02 Nov 2003 16:44:12 -0700)
> Did anything specific lead you to the conclusion that we had finished
> handling his papers?
This is too much. We got the following message.
That message says that he began the process of filling out legal
papers. He sent email to fsf-records, who presumably sent him papers
by snail mail.
Before we install the code, we have to wait for the signed papers to
be received and recorded. (We may also need papers from his employer;
I do not know, but fsf-records would have told him.)
Have you read the file maintain.texi which explains these procedures?
next prev parent reply other threads:[~2003-11-04 14:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-12 14:34 patch for unexmacosx.c: supporting non-prebound dynamic library Nozomu Ando
2003-10-31 20:08 ` Andrew Choi
2003-11-01 23:51 ` Do we need legal papers [was: patch for unexmacosx.c: supporting non-prebound dynamic library] Kim F. Storm
2003-11-02 1:21 ` Andrew Choi
2003-11-02 23:18 ` Richard Stallman
2003-11-02 23:44 ` Do we need legal papers Andrew Choi
2003-11-04 14:25 ` Richard Stallman [this message]
2003-11-04 15:44 ` Andrew Choi
2003-11-04 16:00 ` David Kastrup
2003-11-05 0:19 ` Kim F. Storm
2003-11-05 17:34 ` Dave Carlton
2003-11-05 18:58 ` Joseph C. Slater
2003-11-05 23:32 ` Richard Stallman
2003-11-06 16:24 ` Andrew Choi
2003-11-07 9:03 ` Sébastien Kirche
2003-11-09 23:02 ` Kim F. Storm
2003-11-02 23:18 ` Do we need legal papers [was: patch for unexmacosx.c: supporting non-prebound dynamic library] Richard Stallman
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=E1AH27Y-0007Tc-WE@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=nand@mac.com \
--cc=storm@cua.dk \
/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).