all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Mike Kupfer <mkupfer@alum.berkeley.edu>, emacs-devel@gnu.org
Subject: Re: lm-verify, long copyright line
Date: Thu, 22 Jun 2017 16:26:04 -0700	[thread overview]
Message-ID: <bf6e1e55-d17e-e08e-e33f-8ff65c644c6e@cs.ucla.edu> (raw)
In-Reply-To: <17235.1498171890@alto>

On 06/22/2017 03:51 PM, Mike Kupfer wrote:
> Should I ignore the complaint, or
> reorganize the statement into multiple lines which each contain the
> string "Free Software Foundation", or...?

I wouldn't reorganize the statement, as it's likely to be re-reorganized 
in January 2018 when we update the copyright years automatically. 
Instead, I'd either ignore the complaint or better yet fix lm-verify 
(the latter should be pretty simple, just change a string match to a 
regex match).




  reply	other threads:[~2017-06-22 23:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-22 22:51 lm-verify, long copyright line Mike Kupfer
2017-06-22 23:26 ` Paul Eggert [this message]
2017-06-22 23:57   ` Mike Kupfer
2017-06-23  0:07     ` Paul Eggert
2017-06-23  0:28       ` Mike Kupfer
2017-06-23  4:18         ` Paul Eggert
2017-06-23 16:19           ` Stefan Monnier
2017-06-23 17:13             ` Paul Eggert
2017-06-23 17:59               ` Glenn Morris
2017-06-23 18:33                 ` Paul Eggert
2017-06-24 22:16                   ` Mike Kupfer
2017-06-25  2:01                     ` Paul Eggert
2017-06-25  2:59                       ` Mike Kupfer
2017-06-25 15:10                       ` Stefan Monnier
2017-06-25 16:59                         ` Mike Kupfer
2017-06-25 20:45                         ` Paul Eggert
2017-06-25 20:53                           ` Mike Kupfer
2017-06-25 21:05                             ` 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=bf6e1e55-d17e-e08e-e33f-8ff65c644c6e@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=mkupfer@alum.berkeley.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 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.