OS/161: Local Changes and Version Control

about OS/161 | about System/161 | project news | publications | license | credits
download | guides and resources | documentation | for instructors | bugs | mailing lists

The upstream version control for OS/161 is a nightmare. Each solution set or solution fragment needs to be a branch, which is bad enough; plus when things are under active development it is essential that each changeset be merged from one branch to the next in the right order, never skipping any or going in the wrong order at the risk of creating potentially unfixable problems. Nowadays branches at least are not so painful (whereas OS/161 1.x was done using CVS...) but the tools for managing branches are still not what one would like.

Fortunately, to maintain your own local changes against the upstream version you don't have to buy into most of the hassles.

(the rest of this page coming soon)