patchtrack branches

Your b4 prep branches, against what you posted.

b4 keeps its state in an empty cover commit at the base of each prep branch: the change-id, the next revision to send, and the cover message-id of every version sent. So each branch can show its family’s state, and one of:

• ”as sent in vN”;

• ”vN+1 in preparation: K changed since vN” (compared by git patch-id);

• ”draft: never sent”.

Repositories come from --repo or [b4] repos in the config.

usage: patchtrack branches [-h] [--repo REPO] [-a AUTHOR]
                           [--color {auto,always,never}]

Named Arguments

--repo

default: [b4] repos in the config

Default: []

-a, --author

default: [sync] authors, or every author synced

--color

Possible choices: auto, always, never

Default: 'auto'