Uh oh!
There was an error while loading. Please reload this page.
Correctly determinate the owner in case of shared external storages - #14194
Merged
MorrisJobke merged 1 commit intoFeb 19, 2019
Conversation
nickvergessen
commented
Feb 14, 2019
MemberAuthor
/backport to stable15 |
nickvergessen
commented
Feb 14, 2019
MemberAuthor
/backport to stable14 |
MorrisJobke
commented
Feb 14, 2019
Member
Failing tests: |
Signed-off-by: Joas Schilling <coding@schilljs.com>
nickvergessenforce-pushed
the
bugfix/noid/correctly-determinate-owner-in-case-of-shared-external-storages
branch
from
February 18, 2019 09:57
7705aee to
f66c37bComparenickvergessen
commented
Feb 18, 2019
MemberAuthor
fixed |
MorrisJobke
deleted the
bugfix/noid/correctly-determinate-owner-in-case-of-shared-external-storages
branch
February 19, 2019 09:28
backport to stable15 in #14283 |
backport to stable14 in #14284 |
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
Sign up for freeto 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.
Steps
i. user gets notified
i. user gets notified
i. both users are getting notified
i. only user B gets notified, not the creator