From: Bruno Haible <bruno@clisp.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: libc-alpha@sourceware.org
Subject: Re: published documentation
Date: Sun, 20 Mar 2022 22:08:48 +0100 [thread overview]
Message-ID: <18310683.jiFIW2sfyF@omega> (raw)
In-Reply-To: <2440cc90-93fe-fd38-07a7-cddd9562807d@cs.ucla.edu>
Paul Eggert wrote:
> I fixed that by running this script:
Thank you!
prev parent reply other threads:[~2022-03-20 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 14:40 Bruno Haible
2022-03-20 20:04 ` Paul Eggert
2022-03-20 21:08 ` Bruno Haible [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=18310683.jiFIW2sfyF@omega \
--to=bruno@clisp.org \
--cc=eggert@cs.ucla.edu \
--cc=libc-alpha@sourceware.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).