Change the sync behavior to fit the LTFS format Spec 2.5
#461
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
added 2 commits
May 23, 2024 11:15
- Sync when ltfs.commitMessage or ltfs.sync is written with an UTF-8 string
- Overwrite commit message when index is written because of predefined reasons
- Sync with a predefined reason when ltfs.commitMessage or ltfs.sync
receive an normalized UTF-8 string
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.
Summary of changes
In the LTFS format spec 2.5, behavior of sync is changed.
ltfs.commitMessageis writtenltfs.syncDescription
The changes in this PR make commit massage more specific. It means specified message is always written down to the tape. So there is no need to take care about carry over of the message.
In this PR, I made the changes below.
commit messageis always specified implicitly or explicitlysyncFixes #455
Type of change
Checklist: