> I've seen quite a few false positive, ie. mail with diffs in them > (because people use diffs to illustrate an idea) were treated as > patches. > > One goal I have is to lower patchwork maintenance (ie limit the number > of fixes we need to do by hand). That's a small improvement towards that > direction. > > Signed-off-by: Damien Lespiau <[email protected]>
I like this idea a lot: I don't think this needs to be a per-project setting, however. There's only one "entry point" for submitting patches - parsemail.py - so a flag on this application would be more than adequate for limiting access. This will remove the need for the database migration. What are your thoughts on adding this flag in place of the project setting? Stephen _______________________________________________ Patchwork mailing list [email protected] https://lists.ozlabs.org/listinfo/patchwork
