unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 51122@debbugs.gnu.org
Subject: [bug#51122] [PATCH v2] maint: Factorize po xref translation.
Date: Tue, 12 Oct 2021 15:25:37 -0400	[thread overview]
Message-ID: <5EFA87E6-D0D0-4D28-99D4-2CCC7E00EDD0@lepiller.eu> (raw)
In-Reply-To: <20211012180941.i7c26gyz3yyqsdd6@pelzflorian.localdomain>

Le 12 octobre 2021 14:09:41 GMT-04:00, "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> a écrit :
>On Tue, Oct 12, 2021 at 05:56:23PM +0200, pelzflorian (Florian Pelz) wrote:
>> We definitely want to compile guix/build/po.scm, I think, because it
>> should be run each time a guix-manual.LL.po or guix-cookbook.LL.po
>> file changes.
>
>Then again, is calling guix without compiling necessarily slower than
>the sed script?
>
>Regards,
>Florian

Yes, each time I see the "newer than compiled" message, it takes several minutes.




  reply	other threads:[~2021-10-12 19:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-10 21:32 [bug#51122] [PATCH] maint: Factorize po xref translation Julien Lepiller
2021-10-10 21:37 ` Julien Lepiller
2021-10-11  8:45   ` pelzflorian (Florian Pelz)
2021-10-11 12:46     ` [bug#51122] [PATCH v2] " Julien Lepiller
2021-10-11 17:17       ` pelzflorian (Florian Pelz)
2021-10-11 22:06         ` Julien Lepiller
2021-10-12 15:56           ` pelzflorian (Florian Pelz)
2021-10-12 18:09             ` pelzflorian (Florian Pelz)
2021-10-12 19:25               ` Julien Lepiller [this message]
2021-10-16  2:12                 ` Julien Lepiller
2021-10-16 18:45                   ` pelzflorian (Florian Pelz)
2021-10-17 20:12                     ` bug#51122: " Julien Lepiller

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=5EFA87E6-D0D0-4D28-99D4-2CCC7E00EDD0@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=51122@debbugs.gnu.org \
    --cc=pelzflorian@pelzflorian.de \
    /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).