public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
* [RFC] Updating patchwork patches on commit
@ 2020-12-07  5:48 Siddhesh Poyarekar
  2020-12-07  8:45 ` Florian Weimer
  2020-12-07 16:15 ` DJ Delorie
  0 siblings, 2 replies; 21+ messages in thread
From: Siddhesh Poyarekar @ 2020-12-07  5:48 UTC (permalink / raw)
  To: libc-alpha

[Re-sending because I don't know how to type email addresses.]

Hi,

I have been running some hacked up scripts to update patch state on 
patchwork for every commit that goes into the glibc repository.  The 
script simply walks through commits in a date range, hashes the diffs 
from each ref (using patchwork/hasher.py) and compares it with hashes on 
patchwork.  If the patch as been committed with the diff unchanged, the 
hashes match.  This is very similar to the git hook that patchwork 
ships[1], so I hope to eventually add this into the glibc git hook.

In the last run (2020-12-07), of the 33 commits went in since 
2020-12-01, 19 were found in patchwork and 14 were missing.  The week 
before (2020-11-23 - 2020-12-01) it was 19 found and 9 missing.

This means that diffs of 14 patches were modified before committing. Our 
commit policy explicitly allows this and trusts committers to limit 
these changes to trivial fixes.  However for patchwork usage to be 
valuable (and in the process, improve transparency), a 1:1 
correspondence between git commits and patchwork would be ideal.  That 
is, every commit on git should have at least one[2] patchwork entry. 
This also solves the question "What finally went in?" I've had to ask 
myself repeatedly when cleaning up patchwork state.

We could achieve this without additional busy work by having the git 
hook send out [pushed] emails to the list in addition to glibc-cvs 
(libc-alpha should be spared the private branch traffic of course) 
whenever it sees a commit that it can't find on patchwork.  A nightly 
script can then trivially mark all [pushed] patches as committed.

Thoughts?

Siddhesh

[1] 
https://github.com/getpatchwork/patchwork/blob/master/tools/post-receive.hook
[2] People have been known to send out identical patches repeatedly as 
part of a series.

^ permalink raw reply	[flat|nested] 21+ messages in thread

end of thread, other threads:[~2021-02-12 13:04 UTC | newest]

Thread overview: 21+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-07  5:48 [RFC] Updating patchwork patches on commit Siddhesh Poyarekar
2020-12-07  8:45 ` Florian Weimer
2020-12-07  9:30   ` Siddhesh Poyarekar
2020-12-07 16:15 ` DJ Delorie
2020-12-07 16:39   ` Siddhesh Poyarekar
2020-12-07 17:02     ` DJ Delorie
2020-12-07 18:11       ` Joseph Myers
2020-12-08  2:57         ` Siddhesh Poyarekar
2020-12-08  9:08           ` Andreas Schwab
2020-12-08 10:10             ` Siddhesh Poyarekar
2020-12-16 18:35               ` Girish Joshi
2020-12-16 18:49                 ` Siddhesh Poyarekar
2020-12-17 17:49                   ` Girish Joshi
2020-12-18  4:04                     ` Siddhesh Poyarekar
2020-12-19 13:25                       ` Girish Joshi
2020-12-22 15:13                         ` Girish Joshi
2021-01-06 20:26                           ` Girish Joshi
2021-02-04 15:47                             ` Girish Joshi
2021-02-12  5:25                               ` Siddhesh Poyarekar
2021-02-12  9:02                               ` Siddhesh Poyarekar
2021-02-12 13:04                                 ` Carlos O'Donell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).