From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: Collin Funk <collin.funk1@gmail.com>
Subject: Re: Can we have gnulib-tool.py emit the same copyright header?
Date: Wed, 28 Feb 2024 03:07:52 +0100 [thread overview]
Message-ID: <22133500.sWSEgdgrri@nimes> (raw)
In-Reply-To: <36e3772e-7225-45e9-a2b4-3ea1f5405519@gmail.com>
Hi Collin,
> When creating a Makefile for example, the diff between gnulib-tool and
> gnulib-tool.py is:
>
> diff --git a/lib/gnulib.mk.in b/lib/gnulib.mk.in
> index a718c17c0e8..15d15970051 100644
> --- a/lib/gnulib.mk.in
> +++ b/lib/gnulib.mk.in
> @@ -1,5 +1,5 @@
> ## DO NOT EDIT! GENERATED AUTOMATICALLY!
> -# Copyright (C) 2002-2024 Free Software Foundation, Inc.
> +# Copyright (C) 2024 Free Software Foundation, Inc.
>
> The gnulib-tool.py one only does a single year instead of the range.
>
> This diff is copied from the attached patch:
>
> diff --git a/pygnulib/GLInfo.py b/pygnulib/GLInfo.py
> index 808f11b06f..1759368268 100644
> --- a/pygnulib/GLInfo.py
> +++ b/pygnulib/GLInfo.py
> @@ -80,8 +80,6 @@ class GLInfo(object):
> '''Return formatted string which contains copyright.
> The special __copyright__ variable is used (type is str).'''
> copyright = __copyright__
> - # Per the GNU Coding Standards, show only the last year.
> - copyright = re.compile('^[0-9]*-').sub('', copyright)
> result = 'Copyright (C) %s' % copyright
> return result
When I wrote this piece of code (2022-08-05), it was for the --version
output. I had apparently overlooked that the method GLInfo.copyright
also gets used in other contexts than for processing the --version
option.
> The GNU Maintainer guide seems to disagree with this comment (assuming
> that gnulib-tool.py is not a separate package) [1]. Am I missing
> something or can we make this change?
>
> [1] https://www.gnu.org/prep/maintain/maintain.html#Copyright-Notices
In *files*, the copyright notice should contain the first and the last year
of modification; a range <first>-<last> is OK. [1]
In *--version output*, the copyright notice should contain only the last year.
[2]
Bruno
[1] https://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html
[2] https://www.gnu.org/prep/standards/html_node/_002d_002dversion.html
next prev parent reply other threads:[~2024-02-28 2:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 1:41 Can we have gnulib-tool.py emit the same copyright header? Collin Funk
2024-02-28 2:07 ` Bruno Haible [this message]
2024-02-28 2:19 ` Collin Funk
2024-02-28 2:26 ` Bruno Haible
2024-02-28 2:51 ` Collin Funk
2024-02-28 7:53 ` Collin Funk
2024-02-28 11:00 ` Bruno Haible
2024-02-28 21:18 ` Collin Funk
2024-02-28 21:30 ` Bruno Haible
2024-02-28 21:48 ` Collin Funk
2024-02-28 23:34 ` Bruno Haible
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=22133500.sWSEgdgrri@nimes \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=collin.funk1@gmail.com \
/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.
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).