<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Hi All,</div>
<div><br>
</div>
<div>TL;DR - Everything is fine; there was a minor inconsistency that I fixed. Please pull updates.</div>
<div><br>
</div>
<div>We inadvertently merged one of the proposals that was ratified at the last meeting into master instead of osh_spec_next. I updated the branches to fix this by applying the change to osh_spec_next and reverting the change on master, so the spec is back
in the correct state (master is OpenSHMEM 1.3 and osh_spec_next is draft 1.4).</div>
<div><br>
</div>
<div>Unfortunately, the change has confused the github web UI and it now suggests creating a PR to merge master into osh_spec_next (which would be incorrect, since this would revert the change we ratified). Hopefully this doesn't lead to confusion. If it
does, please let me know and I can fix it (e.g. by merging master to osh_spec_next and re-applying the change from the proposal in question). The fix to un-confuse the github web interface is easy, it's just a little extra churn in the history. If you want
me to fix this, please say so.</div>
<div><br>
</div>
<div>In the future, I'll be sure to check that proposals are based on the correct branch before merging.</div>
<div><br>
</div>
<div>Best,</div>
<div> ~Jim.</div>
</body>
</html>