> Let's start with what I'm not interested in.  I'm not interested in a
> debate on different version control systems or on the usefulness of
> version control in general.
>
> What I am interested in is what *existing* strategies may have been used
> in the past (or are used now) for doing version control using Forths
> that stored source using *true* blocks.
>
> Note carefully that I make two qualifications here:  First, I'm only
> interested in *existing* strategies because I'm looking for something
> that has been proven by others, not an abstract discussion about what
> possibly could be done.  Second, I'm asking about Forth systems that are
> based on *true* blocks, not blocks implemented on top of files since the
> trivial answer in that case would be to version control the files
> holding blocks.
>
> I appreciate that such a version control system might be ultra-minimal
> and not offer features like branching, tagging, differencing, and
> merging, etc..  It might only offer manual roll-back of a specific block
> to a prior state, or possibly a grand snapshot of all blocks captured at
> a particular point in time.  Whatever-- I'm just looking for past
> strategies.