[RFC] parsemail.py: Don't search for patches in replies

Jeremy Kerr jk at ozlabs.org
Mon Feb 10 12:20:06 EST 2014

Hi Markus,

> Make sure we don't attempt to search for a patch in a reply e-mail.
> There are MUAs out there who leave the quoted e-mail intact without
> prepending quote characters such as ">" at the beginning of each line.


> When that happens, parse_patch() thinks the quoted patch is new. The
> result are multiple database entries containing the same patch (one for
> each such reply) when one would really expect a consolidated thread
> containing the entire discussion and only one copy of the patch.

OK, sounds like something that we might be able to address, but I don't
think this is the correct approach (as others have mentioned too). We
don't want to drop follow-ups, as they may contain patches that we need
to track.

Perhaps there's some other way we could identify these replies that
shouldn't be parsed as patches? Could you send an unmodified (mbox-form)
mail that we can take a look at?



More information about the Patchwork mailing list