[PATCH v2 10/11] parsemail: Handle cover letters sent in reply
Stephen Finucane
stephen.finucane at intel.com
Sat Apr 2 01:57:46 AEDT 2016
Some people send cover letters (and therefore series) as replies to
existing series. Apply a second set of heuristics to cover this case:
* The message contains a '[0/n]' marker tag in the subject
* The message is not the root message, but the subject is unique, i.e.
it is not a reply to a cover letter already stored in Patchwork
It is theoretically possible that the message could be a reply to a
cover letter that's been missed, but such occurences should be rare
and only get rarer the longer an instance is running.
Note that there is a third case which is not yet covered: a cover
letter with the same name but a different number of patches. This
will have to wait until series support is fully implemented.
Signed-off-by: Stephen Finucane <stephen.finucane at intel.com>
---
v2: Only save author if we're saving a cover letter
v3: Handle a reply being reparsed as a cover letter
---
patchwork/bin/parsemail.py | 64 ++++++++++++++++++++++++++++++++++------------
1 file changed, 47 insertions(+), 17 deletions(-)
diff --git a/patchwork/bin/parsemail.py b/patchwork/bin/parsemail.py
index 17a8c0d..7280b89 100755
--- a/patchwork/bin/parsemail.py
+++ b/patchwork/bin/parsemail.py
@@ -295,6 +295,23 @@ def find_submission_for_comment(project, refs):
comment = Comment.objects.get(submission__project=project,
msgid=ref)
return comment.submission
+ except Comment.MultipleObjectsReturned:
+ # NOTE(stephenfin): This is a artifact of prior lack of support
+ # for cover letters in Patchwork. Previously all replies to patches
+ # were saved as comments. However, it's possible that someone could
+ # have created a new series as a reply to one of the comments on the
+ # original patch series. For example, '2015-November/002096.html'
+ # from the Patchwork archives. In this case, reparsing the archives
+ # will result in creation of a cover letter with the same message ID
+ # as the existing comment. Follow up comments will then apply to
+ # both this cover letter and the linked patch from the comment
+ # previously created. We choose to apply the comment to the cover
+ # letter. Note that this only happens when running 'parsearchive'
+ # or similar, so it should not affect every day use in any way.
+ comments = Comment.objects.filter(submission__project=project,
+ msgid=ref)
+ # The latter item will be the cover letter
+ return comments.reverse()[0].submission
except Comment.DoesNotExist:
pass
@@ -496,22 +513,35 @@ def parse_mail(mail, list_id=None):
LOGGER.debug('Patch saved')
return patch
- elif refs == [] and x == 0: # cover letters
- if save_required:
- author.save()
-
- cover_letter = CoverLetter(
- msgid=msgid,
- project=project,
- name=name,
- date=date,
- headers=headers,
- submitter=author,
- content=message)
- cover_letter.save()
- LOGGER.debug('Cover letter saved')
-
- return cover_letter
+ elif x == 0: # (potential) cover letters
+ # if refs are empty, it's implicitly a cover letter. If not,
+ # however, we need to see if a match already exists and, if
+ # not, assume that it is indeed a new cover letter
+ is_cover_letter = False
+ if not refs == []:
+ try:
+ CoverLetter.objects.all().get(name=name)
+ except CoverLetter.DoesNotExist: # no match => new cover
+ is_cover_letter = True
+ else:
+ is_cover_letter = True
+
+ if is_cover_letter:
+ if save_required:
+ author.save()
+
+ cover_letter = CoverLetter(
+ msgid=msgid,
+ project=project,
+ name=name,
+ date=date,
+ headers=headers,
+ submitter=author,
+ content=message)
+ cover_letter.save()
+ LOGGER.debug('Cover letter saved')
+
+ return cover_letter
# comments
@@ -525,7 +555,7 @@ def parse_mail(mail, list_id=None):
author.save()
comment = Comment(
- submission=patch,
+ submission=submission,
msgid=msgid,
date=date,
headers=headers,
--
2.0.0
More information about the Patchwork
mailing list