all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: Luis Felipe <luis.felipe.la@protonmail.com>,48187@debbugs.gnu.org
Subject: [bug#48187] [PATCH] website: help: Add Guix's latest manual
Date: Mon, 03 May 2021 11:15:38 -0400	[thread overview]
Message-ID: <FF780FA0-B51B-4109-9598-8D3B066C4566@lepiller.eu> (raw)
In-Reply-To: <8UmQnlT6MS9cVKGVfsf7WZLqOi0-EbqzUNPUDKxOhYgbUbgfWqiwnWHqyeLWZSScRW913J8ecUCUBy-_WBrT0wD9vExrDMudtn4ZrQU-XQo=@protonmail.com>

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

Great! Could you also regenerate the pot for that commit? Since we check it out with the website, the weblate repo simply copies it as is, and might miss translations.

Alternatively, we could remove it from the website repo and rcly on the weblate process to generate it, as we do for the other domains.

Le 3 mai 2021 10:07:12 GMT-04:00, Luis Felipe via Guix-patches via <guix-patches@gnu.org> a écrit :
>Hi,
>
>This patch adds the latest manual to the help page and a corresponding
>entry to the Help menu.
>
>
>---
>Luis Felipe López Acevedo
>https://luis-felipe.gitlab.io/

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

  reply	other threads:[~2021-05-03 15:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-03 14:07 [bug#48187] [PATCH] website: help: Add Guix's latest manual Luis Felipe via Guix-patches via
2021-05-03 15:15 ` Julien Lepiller [this message]
2021-05-03 15:43   ` Luis Felipe via Guix-patches via
2021-05-03 15:37 ` pelzflorian (Florian Pelz)
2021-05-03 16:27   ` Luis Felipe via Guix-patches via
2021-05-03 22:25     ` Julien Lepiller
2021-05-04  6:05     ` pelzflorian (Florian Pelz)
2021-05-04  6:37       ` pelzflorian (Florian Pelz)
2021-05-04 13:25         ` pelzflorian (Florian Pelz)
2021-05-04 14:00           ` Luis Felipe via Guix-patches via
2021-05-04 14:33             ` bug#48187: " pelzflorian (Florian Pelz)

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

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

  git send-email \
    --in-reply-to=FF780FA0-B51B-4109-9598-8D3B066C4566@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=48187@debbugs.gnu.org \
    --cc=luis.felipe.la@protonmail.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.