`.Op Fl Eq' gets rendered as [-] with groff because Eq it's a macro. Escape it to get it rendered correctly. Discussed with bentley. Reported by casaca on the IRC channel, thanks!

committing on behalf of op@, ok by me

stdarg.h is required on NetBSD for variadic definitions.

gotd's session.c file has been split in two, so update the sources to accommodate this change.

at the moment it is indistinguishable from the created tag.

add test_branch_created(). at the moment this is not different from a "normal" commit notification but it'll change in the future and it's handy to have it for an upcoming branch removed notification.

will help to differentiate these notification objects from the others.

When an operation is interrupted add a trailing message to status output which displays the operation and branches involved. This information will be useful when diagnosing problem reports and it helps new users with contextualizing multi-operation work tree state. ok op@

found by op's regress builder

To support the other types of notifications, we can't just peek at the first byte and decide wether it's a short or long format. Refactor the parsing so that there's one main entrypoint, jsonify(), that calls jsonify_comment() or jsonify_comment_short() depending on the format of the line. Other "line types" will be added as a follow-up to support the other notification types.

Split the author/committer in sub-fields, rename author -> committer in the short format parser and cache the author for the long format in case it's the same user as the committer. Put a copy of the first line of the commit message in the "short_message" field. There's some redundancy now, but it's to make consuming easier. ok stsp@

We now know that unveil(2) will never traverse exec. No need to wait with unveil until the editor has been run. ok op@

We now know that unveil(2) will never traverse exec. No need to wait with unveil until the editor has been run. ok op@