On Sun, Oct 13, 2024, at 14:09, karthik nayak wrote:

    It also allows a "ref" file to be a symbolic pointer to another ref
    file by starting with the four-byte header sequence of "ref:".

This is added to talk about how the command de-references symbolic refs,
but it can be misinterpreted to mean that it does support symbolic refs
on the top level.

Do either of you want to take a stab at updating the documentation here?

I have some ideas. I think I should have something ready later this
evening.

-- 
Kristoffer Haugsbakk