Hi Stephen, >> 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?
This means that patchwork will only work for projects (and contributors!) that use git though. I'd prefer we keep patchwork fairly VCS-agnostic. For the setup on patchwork.ozlabs.org, a flag for parsemail means I'd need project-specific configuration outside of the admin system, which seems a bit clunky. Regards, Jeremy _______________________________________________ Patchwork mailing list [email protected] https://lists.ozlabs.org/listinfo/patchwork
