List view
This is the first alpha-testing version. It will focus on improving the repository's disk storage format, thus finally removing the incredible ballooning of storage requirements that would occur in a repository of significant size or frequency of committing (a repository with 10MB of code and 100 commits would require 1GB of storage space for the version history prior to this version, even if all 100 were just changing single characters back and forth). This version will change commits to encode files as patches from their parents, with rules governing how this is to be done. Additionally, tools will be added to manage this encoding. A tool will be added to verify that all commits match their written hashes (to ward against corruption or stealth modification of history), which will generate a warning for mismatched files. Finally, the stash will be modified to be a set of patches, which are taken at stash-time from a base of the latest commit, and will be applied at unstash time as a patch on the working directory.
No due date•0/6 issues closedThis version will not add any new disk-modifying operations, but will introduce some usability enhancements. These will include upgrades to the merging algorithm (actually merging file contents), a command to produce a diff between different references, the index, and/or the working directory, and a command to amend the metadata of the last commit.
No due date•0/4 issues closedThis version will add support for alternative versions of history. It will support branches, tracking multiple heads simultaneously. These branches will support a very primitive sort of merging, with conflicts being resolved on a per-file basis, with no inspection of file contents (beyond comparing the checksums stored in their commits). It will also support creating a stash, which can save work which should not necessarily be on any actual branch (it should not appear in history)
No due date•0/3 issues closed