Skip to content

[stable16] handle storage exceptions when trying to set mtime - #16038

Merged
rullzer merged 2 commits into
stable16from
backport/15889/stable16
Jun 25, 2019
Merged

[stable16] handle storage exceptions when trying to set mtime#16038
rullzer merged 2 commits into
stable16from
backport/15889/stable16

Conversation

@backportbot-nextcloud

Copy link
Copy Markdown

backport of #15889

@rullzerrullzer mentioned this pull request Jun 24, 2019
5 tasks
not all storage backends can handle setting the mtime and they might
not always handle that error correctly.
Signed-off-by: Robin Appelman <robin@icewind.nl>
Signed-off-by: Robin Appelman <robin@icewind.nl>
@rullzer
rullzerforce-pushed the backport/15889/stable16 branch from ad07880 to b22fca4CompareJune 25, 2019 13:58
@ChristophWurstChristophWurst added the 4. to release Ready to be released and/or waiting for tests to finish label Jun 25, 2019
@rullzer
rullzer merged commit 870a330 into stable16Jun 25, 2019
@rullzer
rullzer deleted the backport/15889/stable16 branch June 25, 2019 19:48
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

4. to releaseReady to be released and/or waiting for tests to finish

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@icewind1991@ChristophWurst@rullzer