From: Jay Belanger <belanger@truman.edu>
Cc: belanger@truman.edu
Subject: Re: License correction
Date: Sun, 17 Sep 2006 22:41:41 -0500 [thread overview]
Message-ID: <87d59tvo22.fsf@vh213602.truman.edu> (raw)
In-Reply-To: <E1GOEhO-00073o-Mr@fencepost.gnu.org> (Richard Stallman's message of "Fri\, 15 Sep 2006 10\:29\:46 -0400")
Richard Stallman <rms@gnu.org> writes:
> Would someone please change the licenses on these files to the GPL?
> I'd rather avoid the need to include the LGPL with Emacs.
...
> ./src/gmalloc.c
> ./src/md5.c
> ./src/md5.h
> ./src/strftime.c
...
> Please ack when this is done.
Done.
next prev parent reply other threads:[~2006-09-18 3:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 14:29 License correction Richard Stallman
2006-09-15 17:27 ` Eli Zaretskii
2006-09-15 18:00 ` David Kastrup
2006-09-18 3:41 ` Jay Belanger [this message]
2006-09-18 18:51 ` 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=87d59tvo22.fsf@vh213602.truman.edu \
--to=belanger@truman.edu \
/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).