git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: merlyn@stonehenge.com (Randal L. Schwartz)
To: git@vger.kernel.org
Subject: information for a 60-minute "intro to git" needed
Date: 11 Nov 2006 06:24:20 -0800	[thread overview]
Message-ID: <8664dmxdrf.fsf@blue.stonehenge.com> (raw)


Apparently, in a fit of confusion, I agreed to present a 60-minute "intro to
git" for the Portland (Oregon) Linux Advanced Topics meeting on 20 November.

Since I haven't even started it, I guess it's time to start writing.  I know
about the Documentation/* directory, but have any of you also written
tutorials or presentations on git for your organization?  If so, I'd like to
steal, I mean observe what you've done.  I will make my slides available as
well, under the GFDL or equivalent.

And Linus, if you're in town on the 20th, you should come to the meeting to
make a fool of me and give the real scoop. :) (Only half joking... if you
could make it there, it'd be a real help to me.)

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.

             reply	other threads:[~2006-11-11 14:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-11 14:24 Randal L. Schwartz [this message]
2006-11-11 14:33 ` information for a 60-minute "intro to git" needed 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
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=8664dmxdrf.fsf@blue.stonehenge.com \
    --to=merlyn@stonehenge.com \
    --cc=git@vger.kernel.org \
    /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).