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:

http://tddjs.com/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 
history: https://github.com/augustl/binbin/blob/master/git-walk

And for coolness factor: here's how Christian integrated git-walk stepping 
in Emacs: http://cjohansen.no/en/emacs/live_coding_help_from_git_and_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 git-us...@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Reply via email to