From: Junio C Hamano <junkio@cox.net>
To: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: jnareb@gmail.com, git@vger.kernel.org
Subject: Re: information for a 60-minute "intro to git" needed
Date: Sat, 11 Nov 2006 11:09:17 -0800 [thread overview]
Message-ID: <7vac2xkdgi.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <ej4teo$bjo$1@sea.gmane.org> (Jakub Narebski's message of "Sat, 11 Nov 2006 17:24:56 +0100")
Jakub Narebski <jnareb@gmail.com> writes:
> Petr Baudis wrote:
>
>> and http://git.or.cz/gitwiki/GitLinks for links to plenty
>> of "using git" pages for various projects and other introductory
>> articles.
>
> GitLinks has now links to junio, jdl and pasky slides from OLS,
> and junio slides from OSDL Japan Linux Symposium.
The OSDL Japan one is much more suitable for stealing tutorial
material from than the OLS one, but they took the pages on old
seminars down without telling me, it seems. I've updated the
link in GitLinks page. The presentation is designed to be run
in 25 minutes using the first half of slides (pretty pictures),
followed by a 25 minutes demo (reproducing the second half of
slides).
I think Martin Langhoff promised to make his presentation done
in Mexico available to us sometime ago, but I wonder what
happened to it...
next prev parent reply other threads:[~2006-11-11 19:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-11 14:24 information for a 60-minute "intro to git" needed Randal L. Schwartz
2006-11-11 14:33 ` Petr Baudis
2006-11-11 16:24 ` Jakub Narebski
2006-11-11 16:34 ` Randal L. Schwartz
2006-11-11 19:09 ` Junio C Hamano [this message]
2006-11-11 22:49 ` Martin Langhoff
2006-11-12 4:51 ` Ryan Anderson
2006-11-13 18:58 ` Jon Loeliger
2006-11-13 21:41 ` Christian MICHON
2006-11-17 19:24 ` Jon Loeliger
2006-11-17 19:31 ` Jon Loeliger
2006-11-17 20:27 ` Junio C Hamano
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=7vac2xkdgi.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=merlyn@stonehenge.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.