Not sure I trust patchwork yet

Brendan Cully brendan at kublai.com
Thu Jan 17 00:36:14 CST 2013


On Wednesday, 16 January 2013 at 23:35, Matt Mackall wrote:
> I wrote the patchwork-to-imap-flag script I was wishing for earlier.
> It works as follows:
> 
>  - find all messages marked "[PATCH" in my inbox
>  - find all patches marked "new" or "under review" in patchwork
>  - for each message in my inbox:
>    - if it's in the patch set, flag it
>    - if it's not, unflag it
> 
> Thus, if it has a flag in my inbox, I may not want to delete it just
> yet, as I may need to reply to it or queue it.
> 
> But if it doesn't have a flag, I can delete it without tediously
> cross-referencing it with the rest of my mailbox, crew, or patchwork,
> safe in the knowledge that it's somehow been either dealt with or
> superseded. 
> 
> However, I seem to have spotted several false negatives. Here are a
> couple:
> 
> http://markmail.org/message/2asd5fg73v5bqgzb
> http://markmail.org/message/kt56kjokj2lg7av6
> 
> These two patches do not appear to be anywhere on patchwork.
> 
> (I could simply also flag patches that are unknown to patchwork, but
> that rather defeats the purpose of using patchwork and is also already
> quite slow.)

Couldn't you flip it around and have patchwork flag the messages that
it knows are no longer relevant so you can delete them quickly?


More information about the Mercurial-devel mailing list