From: Simon Marchi <simark@simark.ca>
To: "Luke T. Shumaker" <lukeshu@lukeshu.com>,
"Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org,
"Alfred M. Szmidt" <ams@gnu.org>,
Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH 1/4] readline: Fix examples/rlfe/configure.ac
Date: Mon, 10 Jun 2024 12:51:40 -0400 [thread overview]
Message-ID: <2a28d876-d53b-4f33-9e70-3da9498758e9@simark.ca> (raw)
In-Reply-To: <87r0d5xzz0.wl-lukeshu@lukeshu.com>
On 2024-06-09 23:01, Luke T. Shumaker wrote:
> On Sat, 08 Jun 2024 12:28:58 -0600,
> Maciej W. Rozycki wrote:
>>
>> On Sat, 8 Jun 2024, Maciej W. Rozycki wrote:
>>
>>>> the readline/readline subdirectory, Tom Tromey, 2019-10-05). The
>>>> confure.ac uses a "../"* sequence to get to the top-directory's
>>>
>>> configure.in
>>
>> And FAOD ditto in the change heading.
>
> Thanks for the corrections, I'm including it in v2 (which I'm about to
> submit).
>
> What does "FAOD" stand for?
According to chatgpt:
In a discussion, "FAOD" stands for "For Avoidance of Doubt." It's used
to clarify a point or detail, ensuring there's no misunderstanding
about what's being communicated. This term is particularly common in
written communication, such as emails or formal documents, where
precision in language is crucial to avoid any ambiguity.
Simon
next prev parent reply other threads:[~2024-06-10 16:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 20:11 [PATCH 0/4] Add a ./bootstrap script to automate bundling and generating files Luke T. Shumaker
2024-06-06 20:11 ` [PATCH 1/4] readline: Fix examples/rlfe/configure.ac Luke T. Shumaker
2024-06-08 18:25 ` Maciej W. Rozycki
2024-06-08 18:28 ` Maciej W. Rozycki
2024-06-10 3:01 ` Luke T. Shumaker
2024-06-10 16:51 ` Simon Marchi [this message]
2024-06-06 20:11 ` [PATCH 2/4] Update COPYING files from gnu.org Luke T. Shumaker
2024-06-06 20:11 ` [PATCH 3/4] zlib: Remove files that should certainly not be checked in Luke T. Shumaker
2024-06-07 6:24 ` Jan Beulich
2024-06-07 7:53 ` Luke T. Shumaker
2024-06-10 3:04 ` Luke T. Shumaker
2024-06-08 0:35 ` Luke T. Shumaker
2024-06-06 20:11 ` [PATCH 4/4] Add a ./bootstrap script to automate bundling and generating files Luke T. Shumaker
2024-06-06 20:53 ` Luke T. Shumaker
2024-06-06 20:57 ` Joseph Myers
2024-06-07 8:23 ` Luke T. Shumaker
2024-06-10 19:27 ` Joseph Myers
2024-06-12 7:02 ` Luke T. Shumaker
2024-06-12 12:58 ` Tom Tromey
2024-06-06 20:55 ` [PATCH 0/4] " Luke T. Shumaker
2024-06-10 3:08 ` [PATCH v2 0/5] " Luke T. Shumaker
2024-06-10 3:08 ` [PATCH v2 1/5] readline: Fix examples/rlfe/configure.in Luke T. Shumaker
2024-06-10 22:49 ` Hans-Peter Nilsson
2024-06-10 3:08 ` [PATCH v2 2/5] Update COPYING files from gnu.org Luke T. Shumaker
2024-06-10 3:08 ` [PATCH v2 3/5] zlib: Remove files that should certainly not be checked in Luke T. Shumaker
2024-06-10 3:08 ` [PATCH v2 4/5] readline: Re-generate configure Luke T. Shumaker
2024-06-10 3:08 ` [PATCH v2 5/5] Add a ./bootstrap script to automate bundling and generating files Luke T. Shumaker
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=2a28d876-d53b-4f33-9e70-3da9498758e9@simark.ca \
--to=simark@simark.ca \
--cc=Ralf.Wildenhues@gmx.de \
--cc=ams@gnu.org \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=lukeshu@lukeshu.com \
--cc=macro@orcam.me.uk \
--cc=tromey@adacore.com \
/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).