Johannes Schindelin [off-list ref] writes:
On Thu, 30 Nov 2006, Carl Worth wrote:
quoted
Here's a crazy idea. How about a "git tutorial" builtin or "git example"
or something that would create a repository into some useful state for
demonstrating something.
That sounds fine! Actually, it should be very simple to turn the tutorial
into such a script, displaying the command with an explanation, and
executing the command. It could even call gitk from time to time, so the
user can form a mental model of the ancestor graph.
Doesn't one of our existing t/ scripts do that?
Johannes Schindelin wrote:
On Thu, 30 Nov 2006, Junio C Hamano wrote:
quoted
Johannes Schindelin [off-list ref] writes:
quoted
On Thu, 30 Nov 2006, Carl Worth wrote:
quoted
Here's a crazy idea. How about a "git tutorial" builtin or "git example"
or something that would create a repository into some useful state for
demonstrating something.
That sounds fine! Actually, it should be very simple to turn the tutorial
into such a script, displaying the command with an explanation, and
executing the command. It could even call gitk from time to time, so the
user can form a mental model of the ancestor graph.
Doesn't one of our existing t/ scripts do that?
;-) I did not forget... t1200-tutorial.sh
But it serves a different purpose: it makes sure that we did not break the
commands in the tutorial. (I fear that the script and the tutorial have
diverged a little bit, though).
git-tutorial should not test that, rather it should show the user what is
possible, and encourage playing with git.
Something like Cogito tutorial-script?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Hi,
On Thu, 30 Nov 2006, Junio C Hamano wrote:
Johannes Schindelin [off-list ref] writes:
quoted
On Thu, 30 Nov 2006, Carl Worth wrote:
quoted
Here's a crazy idea. How about a "git tutorial" builtin or "git example"
or something that would create a repository into some useful state for
demonstrating something.
That sounds fine! Actually, it should be very simple to turn the tutorial
into such a script, displaying the command with an explanation, and
executing the command. It could even call gitk from time to time, so the
user can form a mental model of the ancestor graph.
Doesn't one of our existing t/ scripts do that?
;-) I did not forget... t1200-tutorial.sh
But it serves a different purpose: it makes sure that we did not break the
commands in the tutorial. (I fear that the script and the tutorial have
diverged a little bit, though).
git-tutorial should not test that, rather it should show the user what is
possible, and encourage playing with git.
Ciao,
Dscho