Drop extra MIME-Version headers#55
Merged
derrickstolee merged 4 commits intogitgitgadget:mastergitgitgadget/gitgitgadget:masterfrom Dec 26, 2018
Merged
Drop extra MIME-Version headers#55derrickstolee merged 4 commits intogitgitgadget:mastergitgitgadget/gitgitgadget:masterfrom
MIME-Version headers#55derrickstolee merged 4 commits intogitgitgadget:mastergitgitgadget/gitgitgadget:masterfrom
Conversation
Apparently, VS Code's internal formatting interferes with TSLint's (resulting in the formatting seemingly reverting and then re-reverting within half a second upon save). So let's disable VS Code's. While at it, also define the alignment rules. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
... according to the new rules. This (huge) commit best viewed with --color-words. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
When sending mails, the From: or Cc: headers can only contain ASCII characters. Any non-ASCII characters need to be encoded, otherwise the emails will be rejected by the Git mailing list. With this change, the test now also finally learns to test inserting Cc: lines in the GitGitGadget mode (rather than testing the non-GitGitGadget one). This fixes gitgitgadget#29 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
To allow or Cc:ing people whose names contain non-ASCII characters, we tell `format-patch` to always add a `MIME-Version` header. However, `format-patch` itself will add *another* such header if it itself adds encoded non-ASCII characters to the From:, To:, or Cc: header. So let's just undo the damage here. This fixes gitgitgadget#38 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
50e4e2f to
3a0fd42
Compare
Member
Author
|
Please note that this PR is based on #54 and therefore needs that PR to be merged first. |
derrickstolee
approved these changes
Dec 26, 2018
Member
Author
|
@sunshineco any other headers you see that we should not duplicate, either (even if we don't do that right now anyway)? |
Based upon my reading of RFC 2045, the following message headers must be singletons: |
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
As explained in #38, sometimes we end up with mails that have multiple
MIME-Versionheaders.In order to avoid being filed away in the spam folder, let's just post-process the generated mails to remove duplicate
MIME-Versionheaders.