From: Petr Baudis <pasky@suse.cz>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: git@vger.kernel.org,
"Martin Langhoff \(CatalystIT\)" <martin@catalyst.net.nz>
Subject: Re: Scribblings for a cogito/git tutorial
Date: Fri, 21 Oct 2005 22:51:29 +0200 [thread overview]
Message-ID: <20051021205129.GI30889@pasky.or.cz> (raw)
In-Reply-To: <200510171504.j9HF4stb006164@laptop11.inf.utfsm.cl>
Dear diary, on Mon, Oct 17, 2005 at 05:04:54PM CEST, I got a letter
where Horst von Brand <vonbrand@inf.utfsm.cl> told me that...
> I've also been asked around here for a cogito+git tutorial, to that end
> I've made up a script that simulates several developers interacting.
> Hacking around is simulated by patching, ed(1) scripts (merges don't turn
> out the same diff every time), and plain copying new files in. I've set up
> a GPG key with an empty passphrase (comment is "Experimental") to have
> signed tags, etc. in a convenient manner. The idea is to create interesting
> histories (for browsing) and show off the commands in a compact way. If
> only there was a convenient way to run a strech of the (bash) script, look
> at the results, and then resume...
>
> Comments, suggestions, patches are welcome!
>
> Repository of the script and supporting files is at
> <http://pincoya.inf.utfsm.cl/Script.git>
Thanks, it's very nice! If you don't mind (actually, is it / can it be GPL?),
I added it to Cogito as Documentation/tutorial-script/ .
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
next prev parent reply other threads:[~2005-10-21 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 15:04 Scribblings for a cogito/git tutorial Horst von Brand
2005-10-18 2:28 ` David Whistler
2005-10-18 3:12 ` Horst von Brand
2005-10-21 20:51 ` Petr Baudis [this message]
2005-10-21 21:46 ` Horst von Brand
2005-10-23 22:36 ` Petr Baudis
2005-10-21 21:56 ` Horst von Brand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051021205129.GI30889@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=martin@catalyst.net.nz \
--cc=vonbrand@inf.utfsm.cl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).