allow tstamp2.ges and tstamp2.real on metaMark #1151
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kepper
added
Status: Ready To Merge
github-actions
bot
added
the
Component: Core Schema
musicEnfanthen
added
Status: Needs Review
and removed
Status: Ready To Merge
musicEnfanthen
approved these changes
May 25, 2023
rettinghaus
approved these changes
May 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #797 and #767 we were too fast in removing
@tstamp2.gesand@tstamp2.realfrom<metaMark>, which was found when evaluating the diff of v4 and v5. Adding them back in, as agreed on the Charlottesville dev meeting.