| 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: | Ben Franksen via Core-talk <core-talk at aps.anl.gov> |
| To: | mdavidsaver <mdavidsaver at gmail.com> |
| Date: | Fri, 12 Mar 2021 13:55:24 -0000 |
> Precisely. They are annoying, but in the case of errors acceptable as there > is no alternative. I don't like the idea of extending this to warnings, where > from the client prospective everything is working just fine. Hm, yes. A warning that's not seen by the one who causes it is perhaps not worth the hassle. So we have to be defensive here even though I don't like it. -- 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.