unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: François <francois-oss@avalenn.eu>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
	48173@debbugs.gnu.org, maxim.cournoyer@gmail.com
Subject: [bug#48173] [PATCH] maint: Do not xz-compress ISO images.
Date: Mon, 3 May 2021 09:50:27 +0200	[thread overview]
Message-ID: <20210503075027.4egwuyvltjiaa7qv@noop.avalenn.eu> (raw)
In-Reply-To: <20210503021522.2e33ac49@tachikoma.lepiller.eu>

On Mon, May 03, 2021 at 02:15:22AM +0200, Julien Lepiller wrote:
> LGTM, but what should we do about the strings?

sed -i 's/\.iso\.xz/.iso/g' po/doc/guix-manual.*.po

and add that to the patch ?

(notwithstanding some misunderstanding related to how translation works
as I know nothing about that)




  reply	other threads:[~2021-05-03 10:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28 20:18 ISO image: to xz or not to xz? Ludovic Courtès
2021-04-28 20:39 ` Vincent Legoll
2021-04-28 20:41 ` Simon Josefsson via Development of GNU Guix and the GNU System distribution.
2021-05-02 21:16   ` [PATCH] maint: Do not xz-compress ISO images Ludovic Courtès
2021-05-03  0:15     ` [bug#48173] " Julien Lepiller
2021-05-03  7:50       ` François [this message]
2021-05-03 15:39       ` bug#48173: " Ludovic Courtès
2021-05-03 16:35         ` Julien Lepiller
2021-05-04  3:35           ` Maxim Cournoyer
2021-05-03 15:54       ` Ludovic Courtès
2021-04-28 21:16 ` ISO image: to xz or not to xz? Christopher Baines
2021-04-28 21:18 ` Leo Famulari
2021-05-03 16:47 ` Alexandre Oliva
2021-05-03 17:07   ` Leo Famulari
2021-05-03 17:30     ` Vagrant Cascadian
2021-05-03 19:12       ` Tobias Geerinckx-Rice
2021-05-03 19:57         ` Vagrant Cascadian
2021-05-03 17:41   ` Tobias Geerinckx-Rice

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=20210503075027.4egwuyvltjiaa7qv@noop.avalenn.eu \
    --to=francois-oss@avalenn.eu \
    --cc=48173@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=julien@lepiller.eu \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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).