EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: merge requests for dbChannelForDBLinks et al.
From: Ben Franksen via Core-talk <core-talk at aps.anl.gov>
To: Michael Davidsaver <mdavidsaver at gmail.com>, Dirk Zimoch <dirk.zimoch at psi.ch>
Cc: EPICS core-talk <core-talk at aps.anl.gov>
Date: Tue, 14 Apr 2020 12:40:46 +0200
Am 13.04.20 um 07:19 schrieb Michael Davidsaver:
> 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?

Yes. All my branches build on that one, except one. To avoid conflicts
with changes made on branch 7.0 in the meantime, I started by merging
7.0 on top of Dirk's HEAD before I made my own changes.

The one exception is reformat-dbAccess which directly forks off branch 7.0.

> @Ben, which of you MRs do you consider ready for review?  That is,
> where you aren't planning further changes.

All of them. However, the latest one (branch address-modifiers) was
already commented on in detail by Andrew, so I will likely make further
changes there. The others are stable as far as I am concerned.

> 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?

These listed dependencies are bogus, i.e. they were inherited from
previous versions. I will re-submit the two merge proposals with updated
dependencies.

In historical order:

https://code.launchpad.net/~bfrk/epics-base/+git/epics-base/+merge/381153

(trivial code reformat)

https://code.launchpad.net/~bfrk/epics-base/+git/epics-base/+merge/381153

This is a pure refactor with no new features. It only depends on Dirk's
dbChannelForDBLinks.

https://code.launchpad.net/~bfrk/epics-base/+git/epics-base/+merge/381307

The dependency on the listed branch is a left-over from a previous
version. I will re-submit this one. It depends on the previous merge
proposal.

https://code.launchpad.net/~bfrk/epics-base/+git/epics-base/+merge/381307

Similar. The dependency is bogus and needs to be replaced.

Review in progress:

https://code.launchpad.net/~bfrk/epics-base/+git/epics-base/+merge/381628

This is the main feature I have been aiming at. Andrew made a few
comments and suggested a generalization. I am working on that. The
dependency (branch address-modifiers-prerequisites) is an alias for
zero-size-array-request which is merge request 381308.

Cheers
Ben

Attachment: signature.asc
Description: OpenPGP digital signature


References:
merge requests for dbChannelForDBLinks et al. Michael Davidsaver via Core-talk

Navigate by Date:
Prev: Re: MSVC printf/vararg weirdness Michael Davidsaver via Core-talk
Next: [Merge] ~bfrk/epics-base:scalar-get-optimization into epics-base:7.0 Ben Franksen via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024 
Navigate by Thread:
Prev: merge requests for dbChannelForDBLinks et al. Michael Davidsaver 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  <20202021  2022  2023  2024 
ANJ, 14 Apr 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·