From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>,
"fukuri.sai@gmail.com" <fukuri.sai@gmail.com>
Cc: "nvdimm@lists.linux.dev" <nvdimm@lists.linux.dev>,
"qi.fuli@fujitsu.com" <qi.fuli@fujitsu.com>
Subject: Re: [ndctl PATCH 1/5] ndctl, ccan: import ciniparser
Date: Mon, 23 Aug 2021 19:41:32 +0000 [thread overview]
Message-ID: <4395bebebdfbdb17422bfc82368a33fb7048ee60.camel@intel.com> (raw)
In-Reply-To: <CAPcyv4imFbXW2_84QqmT+AmanXAtKXNQgKNEez3EX=o=XLiNjg@mail.gmail.com>
On Mon, 2021-08-23 at 09:48 -0700, Dan Williams wrote:
> On Sun, Aug 22, 2021 at 1:36 PM QI Fuli <fukuri.sai@gmail.com> wrote:
> >
> > Import ciniparser from ccan[1].
> > [1] https://ccodearchive.net/info/ciniparser.html
>
> Hi Qi,
>
> Vishal points out that an updated version of this code is now
> available as a proper library that ships in distributions called
> "iniparser".
>
Here is the link to the project - it seems like it is maintained by the
same person, just outside of ccan, and as a standalone project:
https://github.com/ndevilla/iniparser
next prev parent reply other threads:[~2021-08-23 19:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 20:30 [ndctl PATCH 0/5] make ndctl support global configuration files QI Fuli
2021-08-22 20:30 ` [ndctl PATCH 1/5] ndctl, ccan: import ciniparser QI Fuli
2021-08-23 16:48 ` Dan Williams
2021-08-23 19:41 ` Verma, Vishal L [this message]
2021-08-24 2:30 ` qi.fuli
2021-08-22 20:30 ` [ndctl PATCH 2/5] ndctl, util: add parse-configs helper QI Fuli
2021-08-22 20:30 ` [ndctl PATCH 3/5] ndctl: make ndctl support configuration files QI Fuli
2021-08-22 20:30 ` [ndctl PATCH 4/5] ndctl, config: add the default ndctl configuration file QI Fuli
2021-08-22 20:30 ` [ndctl PATCH 5/5] ndctl, monitor: refactor monitor for supporting multiple config files QI Fuli
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=4395bebebdfbdb17422bfc82368a33fb7048ee60.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=dan.j.williams@intel.com \
--cc=fukuri.sai@gmail.com \
--cc=nvdimm@lists.linux.dev \
--cc=qi.fuli@fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.