After the merge, the content of the main branch at cisco/ChezScheme will be almost the same as the current content of the racket/ChezScheme branch. In other words, we're merging all of the racket/ChezScheme functionality to cisco/ChezScheme. We've worked to ensure that the changes in racket/ChezScheme are not Racket-specific and that the changes preserve Chez Scheme's coherence, character, and quality.
By "content" of the branch being the same as racket/ChezScheme, I mean the content of a checkout using the most recent commit of cisco/ChezScheme after the merge, but the history from both branches will be preserved. Tip: Clone the cisco/ChezScheme repo with `git clone
--filter=blob:none` to avoid eagerly downloading large boot files for
older versions. (That's a useful approach already, even before the merge,
and this tip will appear at the top of the new "README".)
The only substantial difference from the current racket/ChezScheme content is that the merged cisco/ChezScheme will not refer to a Git submodule for pb (portable bytecode) boot files. Instead, pb boot files will be part of the cisco/ChezScheme repo, continuing the way some platform-specific boot files have historically been checked into the cisco/ChezScheme.