bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Simon Josefsson via Gnulib discussion list <bug-gnulib@gnu.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: bug-gnulib <bug-gnulib@gnu.org>
Subject: Re: maint.mk: announcement should not be emailed to the TP when there are no changes
Date: Sat, 04 Feb 2023 22:18:09 +0100	[thread overview]
Message-ID: <87k00xp1ta.fsf@kaka.sjd.se> (raw)
In-Reply-To: <CAOnWdojS0js9rLuca0KT=KbDSfxfDx=7ACou1TTV_TzOefSzKQ@mail.gmail.com> (Reuben Thomas's message of "Sat, 4 Feb 2023 17:18:32 +0000")

[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]

Reuben Thomas <rrt@sc3d.org> writes:

> Using the standard gnulib release procedure for GNU projects,
> coordinator@translationproject.org is automatically emailed for each
> release, but apparently this is not desired. I received this from Benno
> Schulenberg <coordinator@translationproject.org>:
>
> My scripts find zero changes in the msgids.
>>
>> When there are no changes in the POT file, there is no need
>> to announce the (pre)release to me -- it just creates extra,
>> unneeded work for me.
>>
>
> Of course, I can try to catch this manually, but I presume other projects
> are also sending unwanted email like this (unless I'm doing something
> wrong?); can something be done in gnulib?

I manually remove that Cc when not appropriate, or add the following to
cfg.mk for projects without translations:

translation_project_ =

however I realize this is manual work, so I agree with you it could be
improved.

To automatically understand if a cc to the translation project is
necessary or not, I think we'd need access to the previously sent pot
file, no?  I guess we could wget that from somewhere and compare it, but
that seems a bit fragile.  I generally don't like fetching files from
the Internet durings builds, so another approach is to store them in git
and make a comparison there.

Sorry, no real answer, but just some additional thoughts.

/Simon

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]

  reply	other threads:[~2023-02-04 21:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230131191148.LzY9b%rrt@sc3d.org>
     [not found] ` <e451a590-aa9b-cfbb-e63d-82fe7bd3c372@translationproject.org>
2023-02-04 17:18   ` maint.mk: announcement should not be emailed to the TP when there are no changes Reuben Thomas
2023-02-04 21:18     ` Simon Josefsson via Gnulib discussion list [this message]
2023-02-04 21:32       ` Reuben Thomas

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=87k00xp1ta.fsf@kaka.sjd.se \
    --to=bug-gnulib@gnu.org \
    --cc=rrt@sc3d.org \
    --cc=simon@josefsson.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.
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).