From: merlyn@stonehenge•com (Randal L. Schwartz)
To: git@vger•kernel.org
Subject: "intro to git" in Portland Oregon on Monday
Date: 16 Dec 2006 09:06:28 -0800 [thread overview]
Message-ID: <86odq3epnv.fsf@blue.stonehenge.com> (raw)
If you're close enough to drop by, I'm giving my hastily prepared
"intro to git" talk Monday night in Portland Oregon. Details at
<http://article.gmane.org/gmane.org.user-groups.linux.portland/14545>.
If you're in a reviewing mood, I'm slowly updating my draft of the talk at
<http://www.stonehenge.com/pic/Git.pdf>. That's just a temp location
though... I'll push it to archive.org when I've finally presenting it.
Thanks to Junio and (someone else, sorry) for giving me feedback already.
--
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-12-16 17:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=86odq3epnv.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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