| Message ID | 1295260843-19477-1-git-send-email-halsmit@t-online.de |
|---|---|
| State | Accepted |
| Headers | show |
Hi Dirk, > If a mail client wraps the line with the sha, there won't necessarily be > a space after 'commit'. Good idea, applied. I've also committed a testcase for this. Cheers, Jeremy
diff --git a/apps/patchwork/bin/parsemail.py b/apps/patchwork/bin/parsemail.py index 0a9daf5..1b73169 100755 --- a/apps/patchwork/bin/parsemail.py +++ b/apps/patchwork/bin/parsemail.py @@ -136,7 +136,7 @@ def mail_headers(mail): for (k, v) in mail.items()]) def find_pull_request(content): - git_re = re.compile('^The following changes since commit .*' + + git_re = re.compile('^The following changes since commit.*' + '^are available in the git repository at:\n' '^\s*(git://[^\n]+)$', re.DOTALL | re.MULTILINE)
If a mail client wraps the line with the sha, there won't necessarily be a space after 'commit'. Signed-off-by: Dirk Wallenstein <halsmit@t-online.de> --- An example is here: http://lists.freedesktop.org/archives/xorg-devel/2010-November/014836.html apps/patchwork/bin/parsemail.py | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)