unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Glenn Morris <rgm@gnu.org>,
	emacs-devel@gnu.org, Mike Kupfer <mkupfer@alum.berkeley.edu>
Subject: Re: lm-verify, long copyright line
Date: Sun, 25 Jun 2017 11:10:20 -0400	[thread overview]
Message-ID: <jwvfueocde8.fsf-monnier+Inbox@gnu.org> (raw)
In-Reply-To: <aaa6ba84-4234-27bf-821a-7d8aeff9dfb8@cs.ucla.edu> (Paul Eggert's message of "Sat, 24 Jun 2017 19:01:21 -0700")

> Reasonably likely, I'd say, as the tradition outside Emacs is to indent
> copyright notices the same as other text. Let's make lm-verify a bit more
> generous about copyright notice format; this is a good thing to do
> regardless of whether we change update-copyright. I installed the attached
> patch into master; does it suffice to solve the problem?

I think the patch is OK.
But I'd still much prefer the continuation lines to be indented.


        Stefan



  parent reply	other threads:[~2017-06-25 15:10 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
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 [this message]
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

  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=jwvfueocde8.fsf-monnier+Inbox@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=mkupfer@alum.berkeley.edu \
    --cc=rgm@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 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).