-
Notifications
You must be signed in to change notification settings - Fork 263
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
Handle moved messages in MessageStore and message lists #787
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
020bfcb
message: Expect the absence of newTopic for certain moves.
PIG208 b662e1e
message test [nfc]: Extract prepareOrigMessages.
PIG208 31b5c19
message test [nfc]: Rename message move test for accuracy.
PIG208 89bba9b
test [nfc]: Split eg.updateMessageMoveEvent helper.
PIG208 a25020f
message [nfc]: Make displayRecipient nullable.
PIG208 ce999c4
message: Handle moved messages from UpdateMessageEvent.
gnprice a8fc00d
msglist test: Move marker message back and forth.
PIG208 838d5a7
msglist [nfc]: Make narrow mutable for _MessageListPageState.
PIG208 e9b5f6f
msglist: Update narrow when propagateMode is changeAll or changeLater.
PIG208 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
Oops, something went wrong.
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.
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.
nit in commit message:
If we're going to have "Signed-off-by:" lines, let's follow the conventions of how they're used. It's a trailer that comes after the material you're signing off on. Are you signing off on the parts of this commit which you co-authored, or only on other parts? If the former, your "Signed-off-by:" should come after your "Co-authored-by:". (And if the latter, it's not clear what the line could really mean and it's probably best to just leave it out.)
For example usage, go into the Linux kernel repo and try a command like
git log --grep Co-author
.