unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mike Kupfer <mkupfer@alum.berkeley.edu>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: lm-verify, long copyright line
Date: Thu, 22 Jun 2017 17:28:53 -0700	[thread overview]
Message-ID: <19525.1498177733@alto> (raw)
In-Reply-To: Paul's message of "Thu, 22 Jun 2017 17:07:14 -0700." <5fe49025-9604-d6dc-185a-8813132ae17f@cs.ucla.edu>

Paul Eggert wrote:

> On 06/22/2017 04:57 PM, Mike Kupfer wrote:
> > Will the copyright update in 2018 break this?
> 
> Although I don't know offhand, you should be able to find out by
> running the shell command:
> 
> UPDATE_COPYRIGHT_YEAR=2018 admin/update-copyright
> 
> on a scratch copy of the source code.

The good news is that it successfully changes the final year in mh-e.el
from 2017 to 2018.  The bad news is that it removes the indentation in
the second line.

It looks fairly straightforward to change the update-copyright script to
add some indentation when there's a line wrap.  Would that be
acceptable?

mike



  reply	other threads:[~2017-06-23  0:28 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 [this message]
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

  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=19525.1498177733@alto \
    --to=mkupfer@alum.berkeley.edu \
    --cc=eggert@cs.ucla.edu \
    --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 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).