From: Jean-Christophe Helary <jean.christophe.helary@traductaire-libre.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs manuals translation readme
Date: Mon, 19 Feb 2024 14:20:48 +0000 [thread overview]
Message-ID: <F4A5B86E-D56F-4619-8598-518224AAA696@traductaire-libre.org> (raw)
In-Reply-To: <86o7ccpozy.fsf@gnu.org>
> On Feb 19, 2024, at 22:22, Eli Zaretskii <eliz@gnu.org> wrote:
>> I did not think you'd install the file right away
>
> I couldn't know that, given that you didn't update the patch for quite
> some time, and then asked whether anything else needed to be done. I
> took that last message as meaning that you would like this to be
> installed. So I did. Apologies if I misunderstood, but generally
> this is what pinging about a patch means around here.
Sorry. I'll be more careful.
>> and had sent to document to a professional proofreader I work with
>> to polish the wording.
>>
>> This patch includes her modifications and a few small things I had
>> added in between.
>>
>> Would you mind considering the propositions?
>
> Thanks, I installed the changes, and then made a few minor changes of
> my own.
Thank you.
prev parent reply other threads:[~2024-02-19 14:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 1:04 Emacs manuals translation readme Jean-Christophe Helary
2024-02-13 2:25 ` Jean-Christophe Helary
2024-02-13 2:31 ` Po Lu
2024-02-13 3:32 ` Eli Zaretskii
2024-02-13 3:51 ` Jean-Christophe Helary
2024-02-13 4:02 ` Po Lu
2024-02-17 8:55 ` Eli Zaretskii
2024-02-17 15:07 ` Jean-Christophe Helary
2024-02-17 18:18 ` Stefan Kangas
2024-02-17 18:30 ` Eli Zaretskii
2024-02-18 10:45 ` Stefan Kangas
2024-02-18 8:00 ` Eli Zaretskii
2024-02-19 11:13 ` Jean-Christophe Helary
2024-02-19 13:22 ` Eli Zaretskii
2024-02-19 14:20 ` Jean-Christophe Helary [this message]
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=F4A5B86E-D56F-4619-8598-518224AAA696@traductaire-libre.org \
--to=jean.christophe.helary@traductaire-libre.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.