Allow clients of the bridge to set Content-Transfer-Encoding header #516
Conversation
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
…y set This should allow git send-email to apply the transfer encoding desired when using the bridge. Signed-off-by: Damien Zammit <[email protected]>
zamaudio
changed the title
Sign up for free
to 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.
This should allow git send-email to apply the transfer encoding desired when using the bridge.
Therefore, when mailing patches to a mailing list from git send-email, proton-bridge should not mangle the actual mail patches when, for example, .gitconfig contains:
(I was not able to compile this change on old version of Debian to test because my Go is out of date)