2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: [Merge] ~dirk.zimoch/epics-base:FilterForInfoFields into epics-base:7.0 |
From: | Dirk Zimoch via Core-talk <core-talk at aps.anl.gov> |
To: | mp+399414 at code.launchpad.net |
Date: | Fri, 12 Mar 2021 15:58:57 -0000 |
First thing I changed in chfPlugin is to support arbitratily long string arguments, so that I do not need to limit the length of the tag name. Should that change go to a different merge request? Should it completely replace the fixed length "chfString" implementation? (currently only used in the "sync" filter) -- https://code.launchpad.net/~dirk.zimoch/epics-base/+git/epics-base/+merge/399414 Your team EPICS Core Developers is subscribed to branch epics-base:7.0.