]> git.ipfire.org Git - thirdparty/patchwork.git/commit
views: Don't munge the 'From' field of patches v1.1.3
authorDoug Anderson <dianders@chromium.org>
Sat, 19 Nov 2016 19:32:09 +0000 (19:32 +0000)
committerStephen Finucane <stephen@that.guru>
Tue, 31 Jan 2017 19:57:36 +0000 (19:57 +0000)
commit48c0e00a9eef60e40a6f6888df37d599803096dd
treef17fe495e84bb49df82387106b7c7911765646f7
parentdb885f97f4450e005935a94718e009042a1f2bd0
views: Don't munge the 'From' field of patches

At the moment patchwork always uses the official submitter name (as
patchwork understands it) as the "From" for patches that you receive.
This isn't quite what users expect and has some unfortunate
consequences.

The biggest problem is that patchwork saves the "official" name for an
email address the first time it sees an email from them.  If that name
is wrong (or was missing) patchwork will be confused even if future
emails from this person are fixed.  There are similar problems if a
user changes his/her name (get married?).

It seems better to just have each patch report the actual "From" that
was used to send that patch.  We'll still return the submitter in
'X-Patchwork-Submitter' just in case someone wants it.

Conflicts:
patchwork/tests/test_mboxviews.py

Reported-by: Wolfram Sang <wsa@the-dreams.de>
Signed-off-by: Doug Anderson <dianders@chromium.org>
Signed-off-by: Stephen Finucane <stephen@that.guru>
(cherry picked from commit d365402fb98dfb2c4aea4b58346096f85bdfa0c3)
patchwork/tests/test_mboxviews.py
patchwork/views/__init__.py