Then I would need to rebuild the repository when I want to make change to
one of the steps. The point of using branches
is that I can make changes to each step afterwards, and have those changes
propagate through to later steps (by merging).
I guess I could use tags on a single branch to mark different steps, but
when I want to inject a change at one of the steps, I would need a branch
This guy seems to have done what I want (more or less):
The webpage seems down, see google cache link:
On Tue, Jan 4, 2011 at 5:11 PM, Thomas Ferris Nicolaisen
> Maybe you could consider documenting each step as a commit instead? I know
> 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:
> 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
> For more options, visit this group at
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
For more options, visit this group at