<html>#2432: backport Baikal boundary handling fix to release branch
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</td></tr>
<tr><td style='text-align:right'> Status:</td><td>open</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td>ET_2020_05</td></tr>
<tr><td style='text-align:right'> Type:</td><td>bug</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td>EinsteinToolkit thorn</td></tr>
</table>
<p>Comment (by Roland Haas):</p>
<p>Approved for backport in the pull request.</p>
<p>Will inlcude in ET_2020_05_v1 to be created in <a data-is-external-link="true" href="https://bitbucket.org/einsteintoolkit/tickets/issues/2431/review-changes-required-for-gcc-10" rel="nofollow">https://bitbucket.org/einsteintoolkit/tickets/issues/2431/review-changes-required-for-gcc-10</a> </p>
<p>Tested on the clusters already in <a data-is-external-link="true" href="http://einsteintoolkit.org/testsuite_results/index.php" rel="nofollow">http://einsteintoolkit.org/testsuite_results/index.php</a> </p>
<p>If you decide to push on yourself (though it might be best to push all changes on the same day), please make sure to create an updated point-release tag ET_2020_05_v1 pointing to the updated release branch.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2432/backport-baikal-boundary-handling-fix-to'>https://bitbucket.org/einsteintoolkit/tickets/issues/2432/backport-baikal-boundary-handling-fix-to</a></p>
</html>