From: "Ludovic Courtès" <ludo@gnu.org>
To: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
Cc: Guile Devel <guile-devel@gnu.org>
Subject: Re: README issues
Date: Sat, 07 Mar 2020 16:59:10 +0100 [thread overview]
Message-ID: <87eeu4i2b5.fsf@gnu.org> (raw)
In-Reply-To: <A59E065A-9FC6-442A-A613-BFC1AF83B77E@traduction-libre.org> (Jean-Christophe Helary's message of "Wed, 22 Jan 2020 03:18:24 +0900")
Hello,
Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
skribis:
> Good evening everybody, thank you for helping on the IRC channel.
>
> Here is a README patch to minimally document fixes for the issues I had.
>
> Don't hesitate to edit to follow the guile documentation standards of any.
>
> If there is a need to have a FSF disclaimer, I'm OK with that. Let me know how to do that (I already have one for emacs/texinfo/translation in general).
I pushed something similar to what you proposed (slightly less
detailed). Thank you for the patch!
Ludo’.
next prev parent reply other threads:[~2020-03-07 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 18:18 README issues Jean-Christophe Helary
2020-03-07 15:59 ` Ludovic Courtès [this message]
2020-03-07 16:30 ` Jean-Christophe Helary
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eeu4i2b5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=jean.christophe.helary@traduction-libre.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.
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).