bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Reuben Thomas <rrt@sc3d.org>
To: Simon Josefsson <simon@josefsson.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, 4 Feb 2023 21:32:47 +0000	[thread overview]
Message-ID: <CAOnWdoiDAATH=vVMHcVU-0dh1sjctCM_BdSbQ6Jca83YGTZJdQ@mail.gmail.com> (raw)
In-Reply-To: <87k00xp1ta.fsf@kaka.sjd.se>

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

On Sat, 4 Feb 2023 at 21:18, Simon Josefsson <simon@josefsson.org> wrote:

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

Thanks, I hadn't thought of that problem.

-- 
https://rrt.sc3d.org

[-- Attachment #2: Type: text/html, Size: 1142 bytes --]

      reply	other threads:[~2023-02-04 21:33 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
2023-02-04 21:32       ` Reuben Thomas [this message]

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='CAOnWdoiDAATH=vVMHcVU-0dh1sjctCM_BdSbQ6Jca83YGTZJdQ@mail.gmail.com' \
    --to=rrt@sc3d.org \
    --cc=bug-gnulib@gnu.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).