From: Alexander Turenko <alexander.turenko@tarantool.org>
To: Vladimir Davydov <vdavydov.dev@gmail.com>
Cc: Cyrill Gorcunov <gorcunov@gmail.com>,
tml <tarantool-patches@freelists.org>
Subject: Re: [PATCH] box/memtx: Allow to skip tuple memory from coredump
Date: Mon, 13 May 2019 17:36:55 +0300 [thread overview]
Message-ID: <20190513143655.5dh2orfqajf6gr42@tkn_work_nb> (raw)
In-Reply-To: <20190513102121.q5twlgfemojneiqm@esperanza>
> I don't quite like the name: memtx_memory_dontdump. We might want to
> extend it to work on vinyl memory as well one day - I don't think we'd
> want to introduce another cfg parameter for that. What about strip_core?
>
> Alexander, what do you think about the new configuration parameter name?
> Do you have a better name in mind?
I think strip_core is okay and as you pointed will allow us to extend
this feature in the future.
prev parent reply other threads:[~2019-05-13 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 17:26 Cyrill Gorcunov
2019-05-13 10:21 ` Vladimir Davydov
2019-05-13 10:33 ` Cyrill Gorcunov
2019-05-13 14:36 ` Alexander Turenko [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=20190513143655.5dh2orfqajf6gr42@tkn_work_nb \
--to=alexander.turenko@tarantool.org \
--cc=gorcunov@gmail.com \
--cc=tarantool-patches@freelists.org \
--cc=vdavydov.dev@gmail.com \
--subject='Re: [PATCH] box/memtx: Allow to skip tuple memory from coredump' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox