Shawn Pearce [off-list ref] writes:
quoted
Work it around by noticing a wildcard match that attempts to update
a local symbolic ref and ignoring it.
At what point should we just support symrefs on the protocol? :-(
I think it is entirely an orthogonal matter. When we learn that the
other side now has this ref as a symref pointing to this other ref,
an update of the local ref on the RHS of the refspec that has such a
symref on its LHS will not be using the current codepath to call
update_ref() to write the object name thru an existing symref.