Add CC of core-talk
On 2/1/21 12:02 AM, Ben Franksen wrote:
> Am 29.01.21 um 20:07 schrieb Michael Davidsaver via Core-talk:
>> I finally got around to executing a small project which has been on my mind
>> for quite awhile now. This has the potential to be a high visibility change,
>> so I want to run it past a wider audience. (since so few people watch PRs)
>
> If we allow PRs from github, shouldn't we also make them send email to
> core-talk?
I guess, if someone can figure out how to accomplish this.
>> Does this seem like a worthwhile change?
>>
>> https://github.com/epics-base/epics-base/pull/102
>
> Yes.
...
> I have the feeling that these are actually two independent
> proposals/additions (one for EPICS_EXEC_DIR and another one for
> IOCSH_SCRIPT_DIR). I think both are useful. It may or may not help to
> keep that in mind when discussing them.
The patch series is order such that the smaller first patch
can be taken by itself to get EPICS_EXEC_DIR and TOP. I didn't
do a separate PR for this as I see this as all one discussion.
Once Andrew chooses a name for EPICS_EXEC_DIR, I'm planning to
apply this first patch immediately.
The rest will likely need more review since it is also adding
a new public API for path manipulations.
- References:
- iocsh scripts and not using $PWD Michael Davidsaver via Core-talk
- Navigate by Date:
- Prev:
Re: iocsh scripts and not using $PWD Ben Franksen via Core-talk
- Next:
Re: [Merge] ~dirk.zimoch/epics-base:epicsMutexPriorityInheritance into epics-base:7.0 mdavidsaver 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:
Re: iocsh scripts and not using $PWD Michael Davidsaver via Core-talk
- Next:
Build failed: epics-base base-iocsh-auto-paths-614 AppVeyor 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
|