Skip to content
Git implementation for plan 9
C Shell Roff Makefile
Branch: master
Clone or download
Latest commit 3f85007 Sep 6, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
template Import git9 from mercurial repository Jun 29, 2019
LICENSE Import git9 from mercurial repository Jun 29, 2019
README Update docs. Sep 3, 2019
branch Fix some rc bugs (thanks BurnZeZ) Aug 21, 2019
clone Fix some rc bugs (thanks BurnZeZ) Aug 21, 2019
diff Fix some rc bugs (thanks BurnZeZ) Aug 21, 2019
export Import git/import. Sep 3, 2019
fetch.c Improve the way that push works. Jun 30, 2019
fs.c Improve and simplify our breadcrumb trail when walking the file tree. Jul 3, 2019
import Import git/import. Sep 3, 2019
mkfile Remove dead file. Sep 6, 2019
ols.c Import git9 from mercurial repository Jun 29, 2019
proto.c Parse ':'-separated SSH urls. Jul 16, 2019
push Fix some rc bugs (thanks BurnZeZ) Aug 21, 2019
ref.c Implement checking for force pushes Jun 30, 2019
send.c Improve experience with new repositories. Jul 5, 2019


Git for Plan 9: git/fs

All commits in this repository were made with git9 running on 9front.


Plan 9 is a non-posix system. Upstream git has been ported, but feels
distinctly un-plan9ish, and even in its native environment, has been
justifiably tarred and feathered for its user experience.

Git/fs implements a git client for plan 9.  The intent is to support
working with git repositories, without cloning the git interface

Git/fs is usable, but not battle tested. It works for me, and covers
the features I need on a daily basis.


The git/fs program provides a file system mounted on /mnt/git.  It
provides a read-only view into the repository contents to allow
scripts to inspect the data.  Surrounding scripts and binaries will
manipulate the repository contents directly.  These changes will be
immediately mirrored in the file system.

Scripts will generally mount git/fs as needed to do
their work, but if you want to browse the repository
manually, run it yourself. You'll get `/mnt/git` mounted,
with the following contents:

	/mnt/git/object:	The objects in the repo.
	/mnt/git/branch:	The branches in the repo.
	/mnt/git/ctl:		A file showing the status of the repo.
				Currently, it only shows the current branch.
	/mnt/git/HEAD		An alias for the currently checked out
				commit directory.

Visible Differences

The most obvious difference is that Git's index is a bit boneheaded, so I'm
ignoring it.  The index doesn't affect the wire protocol, so this
isn't an interoperability issue, unless you share the same physical
repository on both Plan 9 and Unix.  If you do, expect them to disagree
about the files that have been modified in the working copy.

In fact, the entire concept of the staging area has been dropped, as
it's both confusing and clunky.  There are now only three states that
files can be in: 'untracked', 'dirty', and 'committed'.  Tracking is
done with empty files under .git/index9/{removed,tracked}/path/to/file.

It's implemented in Plan 9 flavor C, and provides tools for writing
repository contents, and a file system for read-only access, which
will mirror the current state of the repository.


Install with `mk install`.


Some usage examples:

	git/clone git://
	cd subdir/name
	git/add foo.c
	diff bar.c /mnt/git/HEAD/

Commits are presented as directories with the following

	author:	A file containing the author name
	hash:	A file containing the commit hash
	parent:	A file containing the commit parents, one per line.
	msg:	A file containing the log message for that commit
	tree:	A directory containing a view of the repository.

So, for example:

	% ls /mnt/git/branch/heads/master
	% cat /mnt/git/branch/heads/master/hash

	# This is the same commit, with the same contents.
	% ls /mnt/git/object/7d539a7c08aba3f31b3913e0efef11c43ea9f9ef

	# what git/diff will hopefully do more concisely soon, filtering
	# out the non-git files.
	ape/diff -ur /mnt/git/branch/heads/master/tree .
	Only in .: .git
	Only in .: debug
	diff -ur /mnt/git/branch/heads/master/tree/fold.myr ./fold.myr
	--- /mnt/git/branch/heads/master/tree/fold.myr	Wed Dec 31 16:00:00 1969
	+++ ./fold.myr	Mon Apr  1 21:39:06 2019
	@@ -6,6 +6,8 @@
	 	const foldexpr : (e : expr# -> std.option(constval))
	+/* Look, diffing files just works, and I don't need any fancy glue! */
	 const foldexpr = {e
	 	match e
	 	| &(`Eident &[.sc=`Sclassenum, .name=name, .ty=`Tyenum &(`Body enum)]):
	Only in .: refs

The following utilities and binaries are provided:

	fs:	The git filesystem.
	fetch:	The protocol bits for getting data from a git server.
	send:	The protocol bits for sending data to a git server.
	save:	The gnarly bits for storing the files for a commit.
	conf:	A program to extract information from a config file.
	clone:	Clones a repository.
	commit:	Commits a snapshot of the working directory.
	log:	Prints the contents of a commmit log.
	add:	Tells the repository to add a file to the next commit.
	walk:	`du`, but for git status.

Supported protocols: git:// and git+ssh://. If someone
implements others, I'll gladly accept patches.


Documentation is sparse.
You can’t perform that action at this time.