summaryrefslogtreecommitdiff
path: root/releasenotes
diff options
context:
space:
mode:
authorStephen Finucane <stephen@that.guru>2018-11-04 14:06:03 +0000
committerStephen Finucane <stephen@that.guru>2018-12-22 18:04:21 +0000
commit841f966b8d54b2f51ab1c498eed6e5391f2546a9 (patch)
tree620f1d78483455f6b06e27048d1e46a3a755b0c0 /releasenotes
parentb1c2e80187008aff472c6509c67f44583cd3334c (diff)
downloadpatchwork-841f966b8d54b2f51ab1c498eed6e5391f2546a9.tar
patchwork-841f966b8d54b2f51ab1c498eed6e5391f2546a9.tar.gz
parser: Ensure whitespace is stripped for long headers
RFC2822 states that long headers can be wrapped using CRLF followed by WSP [1]. For example: Subject: Foo bar, baz Should be parsed as: Foo bar,baz While we were stripping the former, we were not stripping the latter. This mean that we ended up with the following: Foo bar, baz Resolve this. Signed-off-by: Stephen Finucane <stephen@that.guru> Closes: #197
Diffstat (limited to 'releasenotes')
-rw-r--r--releasenotes/notes/issue-197-4f7594db1e4c9887.yaml7
1 files changed, 7 insertions, 0 deletions
diff --git a/releasenotes/notes/issue-197-4f7594db1e4c9887.yaml b/releasenotes/notes/issue-197-4f7594db1e4c9887.yaml
new file mode 100644
index 0000000..2777fbc
--- /dev/null
+++ b/releasenotes/notes/issue-197-4f7594db1e4c9887.yaml
@@ -0,0 +1,7 @@
+---
+fixes:
+ - |
+ Long headers can be wrapped using CRLF followed by WSP (whitespace). This
+ whitespace was not being stripped, resulting in errant whitespace being
+ saved for the patch subject. This is resolved though existing patches and
+ cover letters will need to be updated manually.