From: Reuben Thomas <rrt@sc3d.org>
To: bug-gnulib <bug-gnulib@gnu.org>
Subject: maint.mk: announcement should not be emailed to the TP when there are no changes
Date: Sat, 4 Feb 2023 17:18:32 +0000 [thread overview]
Message-ID: <CAOnWdojS0js9rLuca0KT=KbDSfxfDx=7ACou1TTV_TzOefSzKQ@mail.gmail.com> (raw)
In-Reply-To: <e451a590-aa9b-cfbb-e63d-82fe7bd3c372@translationproject.org>
[-- Attachment #1: Type: text/plain, Size: 912 bytes --]
I am maintaining a2ps, and have recently been making frequent alpha
releases as I attempt to stabilise the result of a massive updating effort
after a long period of quiescence.
The most recent release involves no changes to the gettext strings.
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?
--
https://rrt.sc3d.org
[-- Attachment #2: Type: text/html, Size: 2023 bytes --]
next parent reply other threads:[~2023-02-04 17: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 ` Reuben Thomas [this message]
2023-02-04 21:18 ` maint.mk: announcement should not be emailed to the TP when there are no changes Simon Josefsson via Gnulib discussion list
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='CAOnWdojS0js9rLuca0KT=KbDSfxfDx=7ACou1TTV_TzOefSzKQ@mail.gmail.com' \
--to=rrt@sc3d.org \
--cc=bug-gnulib@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.
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).