patchtrack nudge

Open series that need you: a reply, a ping, or a RESEND.

  • reply owed: someone asked or said something after your last message. A bare tag or an “Applied” asks nothing.

  • ping: a week or more since anyone last wrote.

  • resend: two weeks or more with no human reply at all.

The defaults follow the kernel’s submitting-patches.rst: “wait for a minimum of one week before resubmitting or pinging reviewers”, and it is “ok to resend … after a couple of weeks”. Your own pings restart the clock. [nudge] ping_days and resend_days change the thresholds.

With a mainline tree configured, its repository’s tags show whether the merge window is open (a final vX.Y with no -rc1 after it). Pings and RESENDs then say “after -rc1”: the kernel asks for patience “during busy times like merge windows”. A final tag over three weeks old reads as stale tags, not an open window. --ignore-merge-window or [nudge] merge_window = false turns this off.

--draft DIR writes each ping as a plain-text .eml, threaded to the series and addressed to its recipients, for you to edit and send. A RESEND draft names the b4 send --resend vN command. Nothing is ever sent.

usage: patchtrack nudge [-h] [-a AUTHOR] [-l LIST] [--ping-days PING_DAYS]
                        [--resend-days RESEND_DAYS] [--draft DIR]
                        [--ignore-merge-window] [--color {auto,always,never}]

Named Arguments

-a, --author

default: [sync] authors, or every author synced

-l, --list

only series found by a sync of this inbox

--ping-days

default: [nudge] ping_days, or 7

--resend-days

default: [nudge] resend_days, or 14

--draft

write a ping for each as an .eml file in DIR (never sent)

--ignore-merge-window

do not hold pings for an open merge window (read from a mainline tree’s tags)

Default: False

--color

Possible choices: auto, always, never

Default: 'auto'