Re: [RFC] Auto-posting committed patches to this list?

[Siddhesh Poyarekar <siddhesh@gotplt.org>]

On 3/11/21 10:03 AM, DJ Delorie wrote:
> 
> How much of the problem space would be solved if we only emailed commit
> "patches" directly to the patchwork system?  And how difficult would it
> be to get patchwork to properly match independent commit mails to
> existing patch series?
> 
Currently the matching logic depends on a checksum based on the diff 
part of the patch with the diff part of the commit.  There are some 
limitations in patchwork email parsing because of which on occasion it 
doesn't read the diff correctly, but it largely works.  In general, 
patches sent using git-send-email are parsed correctly and should result 
in correct matching.

There are two problems I'm trying to solve, one is of 1:1 correspondence 
between patchwork state and repo state and that will be solved by 
feeding commit patches directly to patchwork.

The other problem is visibility of commits that don't match mailing list 
content.  We allow, as part of policy, trivial changes to patches before 
they're committed but ideally one should always post the final version 
before commit.  We enforce this ideal case for patches that only contain 
trivial changes.  Having commits that don't match any existing patches 
in patchwork be posted on the mailing list for visibility plugs this 
gap, giving us confidence that every commit that went into the repo was 
at at least one point advertised on the list.

Siddhesh