From: Paul Eggert <eggert@cs.ucla.edu>
To: Emacs development discussions <emacs-devel@gnu.org>
Cc: Adrian Robert <Adrian.B.Robert@gmail.com>
Subject: dubious copyright notices in emacs.tiff, allegro.lua, etc.
Date: Wed, 17 Jan 2018 11:36:43 -0800 [thread overview]
Message-ID: <ef7f9534-b24c-7ad8-fef2-44e894744867@cs.ucla.edu> (raw)
I did a quick pass through the emacs-26 source files and found the
following files with dubious copyright notices. We should fix this one
way or another.
The following image file is used in the GNUstep port:
* nextstep/GNUstep/Emacs.base/Resources/emacs.tiff says 'Copyright (c)
1998 Hewlett-Packard Company' with no permissions notice. Is this
because that TIFF file was created by a tool that inserts that copyright
notice into the image file for some reason? If so, what's the reason?
Can we use a different tool to create a TIFF-format image that doesn't
have this copyright issue? I'll CC: Adrian Robert about this, as he
added that file on 2008-07-15.
The following files were added by Eli on 2015-05-12, as part of a test
suite for etags. As these are just for testing Emacs, presumably it
shouldn't be much trouble to remove them if there are real copyright
issues here:
* test/manual/etags/lua-src/allegro.lua says '-- Copyright (C) 2001-2004
by David A. Capello' and 'Read "LEGAL.txt" for more information.' but
there is no LEGAL.txt.
* test/manual/etags/prol-src/natded.prolog says 'Copyright 1995, Bob
Carpenter' with no permissions notice.
* test/manual/etags/prol-src/ordsets.prolog says 'Copyright(C) 1988,
Swedish Institute of Computer Science' with no permissions otice.
* test/manual/etags/ps-src/rfc1245.ps says 'Copyright (c) 1986,87,89 by
Frame Technology, Inc. All rights reserved.' with no permissions notice.
next reply other threads:[~2018-01-17 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 19:36 Paul Eggert [this message]
2018-01-17 20:16 ` dubious copyright notices in emacs.tiff, allegro.lua, etc Glenn Morris
2018-01-19 8:02 ` Eli Zaretskii
2018-01-21 3:04 ` Paul Eggert
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=ef7f9534-b24c-7ad8-fef2-44e894744867@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=Adrian.B.Robert@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.