Fix renaming faces: Do not delete existing face when renaming #1579
Conversation
This file contains hidden or 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
Member
Author
|
/backport 8908bbd to stable25 |
backportbot-nextcloud
bot
added
the
backport-request
artonge
approved these changes
Jan 9, 2023
Member
Author
|
/compile |
fixes nextcloud/recognize#408 Signed-off-by: Marcel Klehr <[email protected]>
marcelklehr
force-pushed
the
fix/rename-faces
branch
from
a03517e to
2f4e8f5
Compare
Member
Author
|
/compile |
Member
Author
|
/backport 2f4e8f5 to stable25 |
Signed-off-by: nextcloud-command <[email protected]>
1 task
backportbot-nextcloud
bot
removed
the
backport-request
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.
fixes nextcloud/recognize#408
The DAV server seems to delete the destination of a MOVE if it exists. Sed lyf :(