| 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: | merge requests for dbChannelForDBLinks et al. |
| From: | Michael Davidsaver via Core-talk <core-talk at aps.anl.gov> |
| To: | Benjamin Franksen <benjamin.franksen at helmholtz-berlin.de>, Dirk Zimoch <dirk.zimoch at psi.ch> |
| Cc: | EPICS core-talk <core-talk at aps.anl.gov> |
| Date: | Sun, 12 Apr 2020 22:19:38 -0700 |
Dirk/Ben, I tried to make a start of going through the now many (maybe) interrelated merge requests arising to Dirk's dbChannelForDBLinks work. Unfortunately, I have gotten quite confused. Is Dirk's original https://code.launchpad.net/~dirk.zimoch/epics-base/+git/epics-base/+merge/378968 still the place to start? @Ben, which of you MRs do you consider ready for review? That is, where you aren't planning further changes. Two of these are MRs are for branches which depend on other feature branches with do not have active MRs. Should we be looking at these? https://code.launchpad.net/~bfrk/epics-base/+git/epics-base/+merge/381464 https://code.launchpad.net/~bfrk/epics-base/+git/epics-base/+merge/381153 https://code.launchpad.net/~bfrk/epics-base/+git/epics-base/+merge/381307 https://code.launchpad.net/~bfrk/epics-base/+git/epics-base/+merge/381308 https://code.launchpad.net/~bfrk/epics-base/+git/epics-base/+merge/381628