all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: Exceptions for certain files in ELPA?
Date: Tue, 13 Mar 2018 16:42:04 +0200	[thread overview]
Message-ID: <10a3f5a0-873c-0d11-2950-f92958ab721b@yandex.ru> (raw)
In-Reply-To: <jwvr2oo5dx0.fsf-monnier+emacs@gnu.org>

On 3/13/18 3:03 PM, Stefan Monnier wrote:
>>> This can be counted as "trivial" enough not to require copyright
>>> paperwork, indeed.
>> But copyright notices are per-file, right?
> 
> BTW: As soon as we make a single change to that file, it will deserve
> a "Copyright by Free Software Foundation".  What's discussed here,
> rather is whether we should also keep the other copyright line.

Right, but the only change I can see myself applying to it is adding (or 
changing) the copyright line. :-)

>> I expect the build process to be confused.
> 
> The only possible source of annoyance would be "make check_copyrights",
> but this comes with an escape hatch (the copyright_exceptions file), so
> there shouldn't be any problem.

So that's okay to do. Good to know, thanks.



      reply	other threads:[~2018-03-13 14:42 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
2018-03-13 13:03     ` Stefan Monnier
2018-03-13 14:42       ` Dmitry Gutov [this message]

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=10a3f5a0-873c-0d11-2950-f92958ab721b@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.