From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: Re: [9front] Introducing libini
Date: Tue, 28 Feb 2023 12:59:52 +0100 (GMT+01:00) [thread overview]
Message-ID: <7e815b4b-f0d5-4285-a0f1-03e001192bae@sirjofri.de> (raw)
In-Reply-To: <CAH_zEu5JmcHBd0e1uE2WACBSvn8NeCM6yJ7qrjs2mFTP8P4Xpg@mail.gmail.com>
27.02.2023 02:23:47 Nick Owens <mischief@offblast.org>:
> why not ndb?
Because of that:
> On Sun, Feb 26, 2023 at 2:44 PM sirjofri <sirjofri+ml-9front@sirjofri.de> wrote:
>> some people like it, some hate it, but for configuration purposes some really prefer using the ini file format.
And that:
>> [...] array-like structures (using +key=value pairs).
That's it.
sirjofri
prev parent reply other threads:[~2023-02-28 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 22:43 sirjofri
2023-02-27 1:21 ` Nick Owens
2023-02-28 11:59 ` sirjofri [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=7e815b4b-f0d5-4285-a0f1-03e001192bae@sirjofri.de \
--to=sirjofri+ml-9front@sirjofri.de \
--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).