From: Josh Durgin <josh.durgin@inktank.com>
To: Thorsten Behrens <tbehrens@suse.com>,
Danny Al-Gaaf <danny.al-gaaf@bisect.de>
Cc: ceph-devel@vger.kernel.org
Subject: Re: A plea for more tooling usage
Date: Wed, 28 May 2014 14:21:49 -0700 [thread overview]
Message-ID: <5386536D.7020503@inktank.com> (raw)
In-Reply-To: <20140527221935.GA15288@thinkpad.thebehrens.net>
On 05/27/2014 03:19 PM, Thorsten Behrens wrote:
> I wrote:
>> Sage Weil wrote:
>>> If anybody is interested in helping with that effort, pull requests
>>> are very welcome! :)
>>>
> [snip]
>
>> As hinted at in the patch, something like boost::program_options would
>> be nice, but that's a chunk of work & I'd rather hear feedback first
>> this way or the other. For the boost option, not sure if verbose error
>> reporting (the if (oss) parts) would translate over easily, I presume
>> that is deemed important?
>>
> Hi guys,
>
> any further opinion on that? If no one feels strongly, I think I'll
> just go ahead & hack something up with program_options, and see if
> that looks more pleasant. :)
It'd be interesting if you could use boost::program_options just
for the binary-specific flags.
Trying to use it for all options, including those from
common/config_opts.h, is a lot more effort. There was some work towards
that a while ago, though the branch is no longer there:
http://comments.gmane.org/gmane.comp.file-systems.ceph.devel/11139
Josh
next prev parent reply other threads:[~2014-05-28 21:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 13:48 A plea for more tooling usage Daniel Hofmann
2014-05-06 15:19 ` Sage Weil
2014-05-06 15:35 ` Milosz Tanski
2014-05-08 11:37 ` Daniel Hofmann
2014-05-08 12:55 ` Milosz Tanski
2014-05-08 13:19 ` Daniel Hofmann
2014-05-08 14:22 ` Daniel Hofmann
2014-05-15 23:34 ` Thorsten Behrens
2014-05-27 22:19 ` Thorsten Behrens
2014-05-28 21:21 ` Josh Durgin [this message]
2014-05-08 10:37 ` John Spray
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=5386536D.7020503@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=danny.al-gaaf@bisect.de \
--cc=tbehrens@suse.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.