From: Dmitry Gutov <dgutov@yandex.ru>
To: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Exceptions for certain files in ELPA?
Date: Tue, 13 Mar 2018 10:08:41 +0200 [thread overview]
Message-ID: <24cc799d-5f54-bae5-4d9c-c83c113916d0@yandex.ru> (raw)
In-Reply-To: <jwvlgew7q1p.fsf-monnier+gmane.emacs.devel@gnu.org>
On 3/13/18 2:56 AM, Stefan Monnier wrote:
>> 1. mmm-rpm.el. It's ~20 lines, and you could consider its contents to be
>> "configuration" instead of a program. Nevertheless, it's all been written by
>> the same guy who never done copyright assignment, so it doesn't seem fair to
>> write "Copyright by Free Software Foundation" on top of it.
>
> This can be counted as "trivial" enough not to require copyright
> paperwork, indeed.
But copyright notices are per-file, right? I expect the build process to
be confused.
>> 2. mmm-noweb.el. It's much bigger, and reportedly still used by some
>> people. Unfortunately, the author has passed away 7 years ago, so no real
>> chance of copyright assignment.
>>
>> They are not very essential (we could release one or both separately), but
>> have them to be exceptions would make my life simpler.
>
> I wouldn't mind making an exception for this one.
Very good. Do I push the code as is, or do I need to wait for somebody
else's blessing, too?
next prev parent reply other threads:[~2018-03-13 8:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 21:47 Exceptions for certain files in ELPA? Dmitry Gutov
2018-03-13 0:56 ` Stefan Monnier
2018-03-13 4:36 ` Herring, Davis
2018-03-13 7:51 ` Dmitry Gutov
2018-03-13 22:17 ` Richard Stallman
2018-03-13 22:47 ` Dmitry Gutov
2018-03-13 23:09 ` Dmitry Gutov
2018-03-14 14:05 ` Richard Stallman
2018-03-14 16:37 ` Eli Zaretskii
2018-03-14 23:10 ` Richard Stallman
2018-03-14 21:02 ` Dmitry Gutov
2018-03-15 0:04 ` John Wiegley
2018-03-13 8:08 ` Dmitry Gutov [this message]
2018-03-13 13:03 ` Stefan Monnier
2018-03-13 14:42 ` Dmitry Gutov
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=24cc799d-5f54-bae5-4d9c-c83c113916d0@yandex.ru \
--to=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.