| 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 2025 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: [Merge] ~dirk.zimoch/epics-base:FilterForInfoFields into epics-base:7.0 |
| From: | mdavidsaver via Core-talk <core-talk at aps.anl.gov> |
| To: | mp+399414 at code.launchpad.net |
| Date: | Wed, 10 Mar 2021 16:34:37 -0000 |
Adding another member to db_field_log seems like the right approach. I'm wondering whether 'is_owner' is the right distinction to draw. While reviewing, I gave some consideration to adding 'must_lock' to indicate when dbScanLock is needed to for access. This avoids overloading the meaning of '!dtor'. -- https://code.launchpad.net/~dirk.zimoch/epics-base/+git/epics-base/+merge/399414 Your team EPICS Core Developers is requested to review the proposed merge of ~dirk.zimoch/epics-base:FilterForInfoFields into epics-base:7.0.