ok stsp

called in a loop, if we don't clear them we might keep on looping. ok stsp@

We aren't planning to support sending anyway. ok stsp@

Currently we only support the smart protocol with a limited feature set. ok stsp@ tobhe@

The default deny policy is working as expected according to newly added regression test. Tweak this test to use an implicit read-only rule, rather than an explicit one, as stated in the TODO item.

The expected output generated by test scripts was wrong on days with a single-digit date. Found by Omar's regress builder. ok op@

This is just for -portable since jot is not always available. ok stsp@

`.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

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@