-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Merge back 10.12.0 #40682
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge back 10.12.0 #40682
Conversation
This is mainly for streams that don't wrap another one, or use a stream not provided by the native fopen function such as smbclient_open
Signed-off-by: Michiel de Jong <[email protected]>
Signed-off-by: Michiel de Jong <[email protected]>
Signed-off-by: Michiel de Jong <[email protected]>
Signed-off-by: Michiel de Jong <[email protected]>
Revert .htaccess change
Upgrading phpseclib/phpseclib (3.0.18 => 3.0.19)
Ocm via sciencemesh for 10.12
revert logic to expose free_space, but keep availableStorage config
* [tx] updated from transifex * [tx] updated from transifex * make getFrom configurable * fix style * Adjust unit tests for MailNotificationsTest * add changelog * Document remove_sender_display_name system setting * Add unit test cases for when remove_sender_display_name is set to true --------- Co-authored-by: ownClouders <[email protected]> Co-authored-by: Phil Davis <[email protected]>
removing double to
|
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
|
Kudos, SonarCloud Quality Gate passed! |
jnweiger
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR.
This is next on my checklist :-)
Do we want to keep the release-10.12.0 branch around?
It won't hurt for now. But I suppose that if we need to make 10.12.1 then we would create that branch from the 10.12.0 release tag or... |








Description
I made a separate branch name from the current
release-10.12.0branch to do this merge-back. When PRs are merged, GitHub automagically deletes the PR branch, and I don't really want the "real"release-10.12.0branch to accidentally get deleted.How Has This Been Tested?
CI
Types of changes
Checklist: