Subject: |
Re: [Merge] ~freddie-akeroyd/epics-base:msi_close_file into epics-base:3.15 |
From: |
Martin Konrad via Core-talk <[email protected]> |
To: |
[email protected] |
Date: |
Mon, 08 Jul 2019 14:02:02 -0000 |
Review: Approve
Looks good to me. A quick test didn't reveal any problems on Linux.
@Michael: I looked at https://en.cppreference.com/w/c/io/freopen and http://www.cplusplus.com/reference/cstdio/freopen/ and I'm still a little confused. I don't think this change introduces any _new_ issues, though.
--
https://code.launchpad.net/~freddie-akeroyd/epics-base/+git/epics-base/+merge/369763
Your team EPICS Core Developers is requested to review the proposed merge of ~freddie-akeroyd/epics-base:msi_close_file into epics-base:3.15.
- References:
- [Merge] ~freddie-akeroyd/epics-base:msi_close_file into epics-base:3.15 Freddie Akeroyd via Core-talk
- Navigate by Date:
- Prev:
Build completed: epics-base base-7.0-264 AppVeyor via Core-talk
- Next:
Re: [Merge] ~freddie-akeroyd/epics-base:msi_close_file into epics-base:3.15 Freddie Akeroyd 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: [Merge] ~freddie-akeroyd/epics-base:msi_close_file into epics-base:3.15 mdavidsaver via Core-talk
- Next:
Re: [Merge] ~freddie-akeroyd/epics-base:msi_close_file into epics-base:3.15 Freddie Akeroyd 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
|