Skip to content
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

Possibly Replaces email should contain who is suggesting the replacement #1817

Closed
ietf-svn-bot opened this issue Oct 19, 2015 · 5 comments
Closed

Comments

@ietf-svn-bot
Copy link

keyword_easy keyword_sprint owner:bartosz.balazinski@interdigital.com resolution_fixed type_defect | by rjsparks@nostrum.com


The submission tool now allows a submitter to suggest that this submission replaces some other set of drafts. If the submitter doesn't have the permissions to set those replacements directly, mail gets sent either to the relevant group chair, or to the secretariat with the suggestion.

The mail is sent with the datatracker's psuedo-address in the From header. All attribution of the submitter is lost. We should include the submitter's name and email address in the body of the email message that's sent.


Issue migrated from trac:1817 at 2022-03-04 04:46:52 +0000

@ietf-svn-bot
Copy link
Author

@bartosz.balazinski@interdigital.com changed owner from `` to bartosz.balazinski@interdigital.com

@ietf-svn-bot
Copy link
Author

@bartosz.balazinski@interdigital.com changed status from new to closed

@ietf-svn-bot
Copy link
Author

@bartosz.balazinski@interdigital.com changed resolution from `` to fixed

@ietf-svn-bot
Copy link
Author

@bartosz.balazinski@interdigital.com commented


Fixed in ba39077:

This commit fixes bug 1817, commit ready to merge

@ietf-svn-bot
Copy link
Author

@henrik@levkowetz.com commented


Fixed in 408d51c:

Merged in ba39077 from bartosz.balazinski@interdigital.com:
Provide information about who has suggested document replaced-by information in the notification email.

This commit fixes bug 1817,  

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant