• Arkadiusz Hiler's avatar
    parsemail: Catch errors caused by duplicate patches in revision · 8738d513
    Arkadiusz Hiler authored
    Let's assume mail structure with replies like this:
    
    [1/2] Patch 1
      |- [2/2] Patch 2
      |- [2/2] Another Patch 2
    
    When the "Another Patch 2" comes in, it's going to get inserted in the
    same revision at the same place as the original "Patch 2", which results
    in integrity error.
    
    This is the single most common reason for administration notifications.
    
    There is not really much we can do, as the reasons for such emails are
    so ambiguous that the best we can do is to discard them, just like we
    are doing now. So let's make it silent.
    Signed-off-by: Arkadiusz Hiler's avatarArkadiusz Hiler <arkadiusz.hiler@intel.com>
    8738d513
Name
Last commit
Last update
docs Loading commit data...
git-pw Loading commit data...
htdocs Loading commit data...
lib Loading commit data...
patchwork Loading commit data...
templates Loading commit data...
tests Loading commit data...
tools Loading commit data...
.gitignore Loading commit data...
.gitlab-ci.yml Loading commit data...
COPYING Loading commit data...
Dockerfile.testing Loading commit data...
README.md Loading commit data...
manage.py Loading commit data...
tox.ini Loading commit data...