From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] mecurial
Date: Mon, 31 Jan 2022 16:16:51 +0000 [thread overview]
Message-ID: <71174429-0F9A-4E80-AD29-7D5C0C51755E@stanleylieber.com> (raw)
In-Reply-To: <e4525f2f-dba0-473d-969f-e25c72786b42@sirjofri.de>
On January 31, 2022 7:05:15 AM UTC, sirjofri <sirjofri+ml-9front@sirjofri.de> wrote:
>
>31.01.2022 00:06:48 sl@stanleylieber.com:
>
>>> http://fqa.9front.org/fqa8.html#8.12.3
>>
>> i have fixed the documentation.
>
>With a small typo: lovee instead of loves ;)
>
>Thanks for fqa!
>
>sirjofri
>
thanks
next prev parent reply other threads:[~2022-01-31 16:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 20:09 thinktankworkspaces
2022-01-30 21:08 ` Stanley Lieber
2022-01-30 23:06 ` sl
2022-01-31 7:05 ` sirjofri
2022-01-31 16:16 ` Stanley Lieber [this message]
2022-02-02 18:02 ` thinktankworkspaces
2022-02-02 20:08 ` Stanley Lieber
2022-02-02 19:04 ` thinktankworkspaces
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=71174429-0F9A-4E80-AD29-7D5C0C51755E@stanleylieber.com \
--to=sl@stanleylieber.com \
--cc=9front@9front.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 NNTP newsgroup(s).