patchtrack check

Look for every posted patch in the trees.

Only commits after the posting that touch the posted files are read, which takes seconds even on linux-next. Matchers, strongest first:

• message-id: the posting’s message-id in a Link: or Message-ID: trailer (b4 adds one). A message-id cited elsewhere in a commit message names some other patch and does not count;

• patch-id: equal git patch-id --stable;

• subject: the same subject and author, with a changed diff.

Not finding a patch is stored as a result too, with the tree’s commit and the time. A found commit that a later commit in the same tree reverts does not count (unless that revert was itself reverted).

usage: patchtrack check [-h] [-a AUTHOR] [-t TREE] [--fetch]

Named Arguments

-a, --author

default: every author synced

-t, --tree

default: every tree

--fetch

fetch trees that have a –url first

Default: False