bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Collin Funk <collin.funk1@gmail.com>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Subject: Re: Can we have gnulib-tool.py emit the same copyright header?
Date: Tue, 27 Feb 2024 18:19:15 -0800	[thread overview]
Message-ID: <77a35fc5-e06c-45e7-ab8f-d52a8b91519f@gmail.com> (raw)
In-Reply-To: <22133500.sWSEgdgrri@nimes>

On 2/27/24 6:07 PM, Bruno Haible wrote:
> 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.

Ah I see. I probably should have grep'd for that function because I
didn't notice it was used there.

> 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]

That makes sense, thanks. I tried to run --version and got this:

[collin@debian gnulib]$ gnulib-tool.py --version
Traceback (most recent call last):
  File "/home/collin/.local/src/gnulib/pygnulib/main.py", line 1197, in <module>
  File "/home/collin/.local/src/gnulib/pygnulib/main.py", line 442, in main
    % (info.package(), info.date(), version, info.copyright(),
  File "/home/collin/.local/src/gnulib/pygnulib/GLInfo.py", line 109, in date
    result = pattern.findall(result)[0]
IndexError: list index out of range

So, I'll have a look at that fixing that. :)


  reply	other threads:[~2024-02-28  2:19 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
2024-02-28  2:19   ` Collin Funk [this message]
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:

  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=77a35fc5-e06c-45e7-ab8f-d52a8b91519f@gmail.com \
    --to=collin.funk1@gmail.com \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \


* 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).