From: Julien Lepiller <julien@lepiller.eu>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: "pelzflorian \(Florian Pelz\)" <pelzflorian@pelzflorian.de>,
"48637@debbugs.gnu.org" <48637@debbugs.gnu.org>
Subject: [bug#48637] [PATCH] website: Add publications page
Date: Wed, 26 May 2021 14:42:28 -0400 [thread overview]
Message-ID: <96A1F1AB-15C9-46E9-B2F3-47C9C292224A@lepiller.eu> (raw)
In-Reply-To: <HcGISC2zIGVxeg_Hafs_b_H3LEi9QfwPxJumsUq5EsE5e8oKy-JH0UB53r3U0JLVS-42bGq8D6xE0MdENpdQKTHT2w3yEnTlUhbMiHoCR0w=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 736 bytes --]
Absolutely, let's take care of that later, in a separate patch. I think your patch is in a very good shape now. Do you have commit access?
Le 26 mai 2021 14:25:48 GMT-04:00, Luis Felipe <luis.felipe.la@protonmail.com> a écrit :
>On Wednesday, May 26, 2021 5:41 PM, Julien Lepiller
><julien@lepiller.eu> wrote:
>
>> Since last time we calked, I changed che script that updates weblate,
>so it now ignores the checked out pot file and regenerates it for
>weblate. Maybe we should now drop it entirely?
>
>Ah, right. But it would be better to do that in a separate patch,
>right? To decide what can be removed. Because the sexp-xgettext script
>would still be useful to check that new translation strings are well
>formed.
[-- Attachment #2: Type: text/html, Size: 1074 bytes --]
next prev parent reply other threads:[~2021-05-26 18:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 23:35 [bug#48637] [PATCH] website: Add publications page Luis Felipe via Guix-patches via
2021-05-25 13:44 ` pelzflorian (Florian Pelz)
2021-05-25 14:37 ` Luis Felipe via Guix-patches via
2021-05-25 18:21 ` pelzflorian (Florian Pelz)
2021-05-25 19:46 ` Luis Felipe via Guix-patches via
2021-05-25 19:58 ` Julien Lepiller
2021-05-25 20:16 ` Luis Felipe via Guix-patches via
2021-05-26 2:03 ` Julien Lepiller
2021-05-26 10:00 ` pelzflorian (Florian Pelz)
2021-05-26 14:06 ` Luis Felipe via Guix-patches via
2021-05-26 17:41 ` Julien Lepiller
2021-05-26 18:25 ` Luis Felipe via Guix-patches via
2021-05-26 18:42 ` Julien Lepiller [this message]
2021-05-26 19:05 ` Luis Felipe via Guix-patches via
2021-05-25 18:35 ` pelzflorian (Florian Pelz)
2021-05-25 19:14 ` Luis Felipe via Guix-patches via
2021-05-28 11:06 ` Ludovic Courtès
2021-05-28 15:20 ` Luis Felipe via Guix-patches via
2021-05-29 10:25 ` Ludovic Courtès
2021-06-02 19:31 ` Luis Felipe via Guix-patches via
2021-06-02 20:28 ` Julien Lepiller
2021-06-02 21:52 ` Luis Felipe via Guix-patches via
2021-06-02 23:28 ` Julien Lepiller
2021-06-03 9:40 ` Ludovic Courtès
2021-06-03 10:37 ` Julien Lepiller
2021-06-03 13:39 ` Luis Felipe via Guix-patches via
2021-06-03 19:50 ` Luis Felipe via Guix-patches via
2021-06-03 20:37 ` Ludovic Courtès
2021-06-03 21:50 ` Luis Felipe via Guix-patches via
2021-06-04 15:38 ` 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=96A1F1AB-15C9-46E9-B2F3-47C9C292224A@lepiller.eu \
--to=julien@lepiller.eu \
--cc=48637@debbugs.gnu.org \
--cc=luis.felipe.la@protonmail.com \
--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).