From: Jesper Harder <harder@phys.au.dk>
Subject: Re: Using the ANSI standard for info-look
Date: Mon, 27 Jun 2005 10:40:29 +0200 [thread overview]
Message-ID: <87r7eofb0i.fsf@Jesper-Harders-Computer.local> (raw)
In-Reply-To: <E1DmmJQ-0004GW-Mj@fencepost.gnu.org> (Richard M. Stallman's message of "Mon, 27 Jun 2005 01:37:40 -0400")
"Richard M. Stallman" <rms@gnu.org> writes:
> Any objection to the patch below?
> It corrects the regexp for Lisp symbols (to be like the one used for elisp),
> it corrects the case-sensitivity, and it adds an entry to use the Texinfo
> rendition of the ANSI CL standard if available.
>
> Please don't add the reference to the ANSI standard. It is not free.
True. Although, it might turn out that /is/ public domain. According
to Kent Pitman:
Lars Brinkhoff <lars.s...@nocrew.org> writes:
> How about the Common Lisp dpANS documents? I was under the impression
> that they were released under public domainish terms, but now that I
> look, I can't find any copyright notice.
You're right that there isn't a proper notice per se. Documents do
exist (but are not on display publicly) that would show that the legal
intent was to have placed them into the public domain, even though we
botched the final execution of that. A good intellectual property
lawyer would tell you that this means the legal status is messy, but
what that really means (I believe) is that those who paid for its
creation could (hypothetically) have grounds to make a claim that it
was encumbered in some way, that is, to assert that they have some
right of ownership. But since all of those parties at one time or
another signed into this system of contracts identifying that the
intent was to make a public domain document, I don't personally think
they would succeed.
next prev parent reply other threads:[~2005-06-27 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-26 18:13 Using the ANSI standard for info-look Stefan Monnier
2005-06-26 19:38 ` Jesper Harder
2005-06-27 5:37 ` Richard M. Stallman
2005-06-27 8:40 ` Jesper Harder [this message]
2005-06-28 4:16 ` Richard M. 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=87r7eofb0i.fsf@Jesper-Harders-Computer.local \
--to=harder@phys.au.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).