Eh, why not? Took direction from this statement. (and this one)
I got bored, and the above reference caught my eye. I thought it was interesting homework, so i tried it. Originally intended to write it procedurally in C, but ended up writing it in C++ after being quickly reminded of my place by C-strings. Also the filesystem module abstraction in cpp appeals to me over making linux-specific syscalls.
Currently, it can track files/directories and make commits. I will implement as much as is specified in the above references, and will move forward if intellectually curious. The current commit strategy is hilariously suboptimal, and i will change that when i get to actually studying version control systems.
Branching capabilities are available, but merging is not yet supported.
Took about a day and a half to roll out this version.
Currently works reliably on Linux systems. Use make compile to build the binary and then use ./vcs init to intialize a repo.
Use ./vcs add <filename> to track a file.
Use ./vcs rm <filename> to remove a file from tracking (not from filesystem).
Use ./vcs commit -m <message> to make a commit ONLY when you are at the head of a branch.
Use ./vcs checkout -b <branch-name> to create a new branch, provided it does not exist.
Use ./vcs checkout <commit-id> or ./vcs checkout <branch-name> to checkout a specific commit or branch.
Use ./vcs branch to see a list of all branches.