From: Mike Kupfer <mkupfer@alum.berkeley.edu>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Glenn Morris <rgm@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: lm-verify, long copyright line
Date: Sat, 24 Jun 2017 15:16:49 -0700 [thread overview]
Message-ID: <5432.1498342609@alto> (raw)
In-Reply-To: Your message of "Fri, 23 Jun 2017 11:33:46 -0700." <80ca5e28-5911-7ef8-09ec-be4558972208@cs.ucla.edu>
Paul Eggert wrote:
> I suppose someone should change either
> lm-verify or Gnulib to fix the incompatibility between the two
> approaches.
The change to Gnulib is a one-liner:
--- update-copyright~ 2017-06-22 17:16:28.604027480 -0700
+++ update-copyright 2017-06-24 15:08:43.626795139 -0700
@@ -243,7 +243,7 @@
|| ($stmt =~ s/^([\S]+)(?: |$)//))
{
my $line = $1;
- $stmt_wrapped .= $stmt_wrapped ? "$eol$prefix" : $leading;
+ $stmt_wrapped .= $stmt_wrapped ? "$eol$prefix " : $leading;
$stmt_wrapped .= $line;
}
else
I guess the question is how likely would this be to introduce a new set
of problems.
mike
next prev parent reply other threads:[~2017-06-24 22:16 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 [this message]
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=5432.1498342609@alto \
--to=mkupfer@alum.berkeley.edu \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--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).