unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org
Subject: Pushing a huge nls commit
Date: Wed, 14 Jul 2021 15:46:31 -0400	[thread overview]
Message-ID: <2EEA4675-DCF9-47B6-8A54-98B06E8A7D02@lepiller.eu> (raw)

Hi Guix!

Since last release, there have been some changes to the strings in guix and the manual. Our switch to weblate allows for a rolling translation workflow, so there have been significant changes to the translations.

I'd like to run "make download-po" on a more or less regular basis (maybe once a month?). However, the commits cannot be easily reviewed or split really well. This morning, I tried and got a commit:

52 files changed, 191755 insertions (+), 165535 deletions (-)

Note that weblate automatically updates the msgids in the po files, so most of the changes are actually in the English sentences, not in the translations themselves.

Is it ok to push such a big change to master after checking it doesn't break anything? How regularly should that happen?


             reply	other threads:[~2021-07-19 10:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14 19:46 Julien Lepiller [this message]
2021-07-19 12:15 ` Pushing a huge nls commit Efraim Flashner
2021-07-25 20:05   ` Ludovic Courtès

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2EEA4675-DCF9-47B6-8A54-98B06E8A7D02@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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