Maybe you could consider documenting each step as a commit instead? I know 
the author of Test-Driven JavaScript Development did this his example code:

Basically, each tutorial is a git-repository with a number of commits. Each 
commit is a step in the tutorial, so you can walk through it and see what 
the code is like in each step.

Here's a ruby script that enables you to walk up and down Git 

And for coolness factor: here's how Christian integrated git-walk stepping 
in Emacs:

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to