Open ekluzek opened 4 years ago
link to #987
I don't think we should do this on the release-clm5.0 branch anymore. But, we do want it on main development still.
Yes, I think we want this feature available on the development branch. Thanks Erik
On Wed, Feb 2, 2022 at 8:46 PM Erik Kluzek @.***> wrote:
I don't think we should do this on the release-clm5.0 branch anymore. But, we do want it on main development still.
— Reply to this email directly, view it on GitHub https://github.com/ESCOMP/CTSM/issues/922#issuecomment-1028574693, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB5IWJG7HJDGMQILCF4QSUTUZH3APANCNFSM4KRUUQUA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID: @.***>
Automatically turn on the anomaly forcing when ISSP compsets are being used. This should go on both release-clm5.0 and master.
The primary change is in cime, which should go on maint-5.6 as well as master.
ESMCI/cime/#3391
Periodically changes in cime from maint-5.6 are automatically moved to master.