From: zimoun <zimon.toutoune@gmail.com>
To: Julien Lepiller <julien@lepiller.eu>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 38108@debbugs.gnu.org
Subject: [bug#38108] [PATCH] doc: Fix typos.
Date: Fri, 13 Dec 2019 12:27:40 +0100 [thread overview]
Message-ID: <CAJ3okZ2NF+6Xj-_MPpHReGQ5gCoNYqYnsCjy4vNyj8hH9e2U1A@mail.gmail.com> (raw)
In-Reply-To: <33570FF9-B17A-4E08-A3F8-331D1B9DD51C@lepiller.eu>
Hi Julien and Ludo,
On Fri, 13 Dec 2019 at 11:19, Julien Lepiller <julien@lepiller.eu> wrote:
> Sorry I didn't see the message before!
I fully understand! :-)
Busy by more important and interesting stuff (phd, jres, etc.)
> I'm fine with the changes. For now, our workflow is to translate only on a short period of time before each release. This kind of change will invalidate the translation of all affected sentences until the next translation round, which is annoying, but as long as you don't fix the manual for 1.0.1, it should be fine.
The patches does not apply anymore because the doc has changed in the
meantime. Life happens. :-)
I can send another patch that will apply... but because it is boring
and not fun at all, are the "pushers" not too busy now? to avoid to do
again the boring-and-not-fun stuff.
> I'd like to improve our workflow at some point, but that's another discussion :)
If you are coming to the Guix Days, we could arrange a slot to discuss
what could be improved and how. :-)
Cheers,
simon
next prev parent reply other threads:[~2019-12-13 11:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 18:50 [bug#38108] [PATCH] doc: Fix typos zimoun
2019-11-08 14:10 ` Giovanni Biscuolo
2019-11-09 11:40 ` zimoun
2019-11-08 22:41 ` Ludovic Courtès
2019-11-09 12:14 ` zimoun
2019-11-09 21:53 ` Ludovic Courtès
2019-11-11 20:52 ` zimoun
2019-12-02 12:57 ` zimoun
2019-12-13 10:19 ` Julien Lepiller
2019-12-13 11:27 ` zimoun [this message]
2019-12-13 11:55 ` Julien Lepiller
2020-05-22 0:01 ` [bug#38108] doc: Fix typos -- parenthesis dot zimoun
2020-05-22 0:08 ` zimoun
2020-05-22 1:31 ` Julien Lepiller
2020-05-22 8:01 ` zimoun
2020-05-22 18:32 ` Leo Famulari
2020-05-25 9:43 ` zimoun
2020-05-25 13:23 ` bug#38108: " Julien Lepiller
2020-05-26 7:57 ` [bug#38108] " zimoun
2020-05-25 17:33 ` Leo Famulari
2019-11-11 20:11 ` [bug#38108] [PATCH] doc: Fix typos zimoun
2020-05-21 23:55 ` [bug#38108] [PATCH v2] " zimoun
2020-05-22 0:03 ` [bug#38108] [PATCH v3] " zimoun
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=CAJ3okZ2NF+6Xj-_MPpHReGQ5gCoNYqYnsCjy4vNyj8hH9e2U1A@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=38108@debbugs.gnu.org \
--cc=julien@lepiller.eu \
--cc=ludo@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).