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
- Replies:
- Re: merge requests for dbChannelForDBLinks et al. Ben Franksen via Core-talk
- Navigate by Date:
- Prev:
Re: [Merge] ~bfrk/epics-base:scalar-get-optimization into epics-base:7.0 mdavidsaver via Core-talk
- Next:
MSVC printf/vararg weirdness Michael Davidsaver via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Build failed: epics-base base-integration-459 AppVeyor via Core-talk
- Next:
Re: merge requests for dbChannelForDBLinks et al. Ben Franksen via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
|