From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Linus Torvalds <torvalds@osdl.org>
Cc: Timo Hirvonen <tihirvon@gmail.com>,
junkio@cox.net, linux@horizon.com, git@vger.kernel.org
Subject: Re: as promised, docs: git for the confused
Date: 12 Dec 2005 12:39:39 -0800 [thread overview]
Message-ID: <86y82qyrqs.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0512121010550.15597@g5.osdl.org>
>>>>> "Linus" == Linus Torvalds <torvalds@osdl.org> writes:
Linus> So instead of teaching people about "git-read-tree --reset HEAD" etc that
Linus> you'd never know on your own, just teach about "git reset". And not
Linus> bothering with the "git-write-tree + git-commit-tree + git-update-ref"
Linus> approach, just make people use "git commit" from the very beginning.
I learned more by reading the cg-tutorial, at least from the user
perspective. I then went back to the git-tutorial, and was able to
finally understand that these commands are worth ignoring. :)
--
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.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2005-12-12 20:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7vbqzrcmgr.fsf@assigned-by-dhcp.cox.net>
2005-12-09 5:43 ` as promised, docs: git for the confused linux
2005-12-09 9:43 ` Petr Baudis
2005-12-09 14:01 ` linux
2005-12-09 16:49 ` Randy.Dunlap
2005-12-09 19:12 ` Junio C Hamano
2005-12-09 21:54 ` linux
2005-12-09 23:23 ` Junio C Hamano
2005-12-12 16:34 ` Linus Torvalds
2005-12-12 17:53 ` Timo Hirvonen
2005-12-12 18:18 ` Linus Torvalds
2005-12-12 20:39 ` Randal L. Schwartz [this message]
2005-12-13 3:58 ` Joshua N Pritikin
2005-12-13 3:59 ` Randal L. Schwartz
2005-12-13 5:19 ` Junio C Hamano
2005-12-13 5:29 ` Linus Torvalds
2005-12-13 7:18 ` H. Peter Anvin
2005-12-13 8:01 ` Junio C Hamano
2005-12-13 13:58 ` Randal L. Schwartz
2005-12-13 21:16 ` Tip of the day: archaeology Junio C Hamano
2005-12-13 21:54 ` Linus Torvalds
2005-12-13 22:19 ` Junio C Hamano
2005-12-12 17:54 ` as promised, docs: git for the confused Junio C Hamano
2005-12-13 0:22 ` [PATCH] Everyday: some examples Junio C Hamano
2005-12-09 21:33 ` as promised, docs: git for the confused Petr Baudis
2005-12-09 5:44 ` linux
2005-12-10 1:22 ` Junio C Hamano
2005-12-10 8:00 ` Junio C Hamano
2005-12-10 10:56 ` linux
2005-12-04 21:34 git-name-rev off-by-one bug Petr Baudis
2005-12-08 6:34 ` as promised, docs: git for the confused linux
2005-12-08 21:53 ` Junio C Hamano
2005-12-08 22:02 ` H. Peter Anvin
2005-12-09 0:47 ` Alan Chandler
2005-12-09 1:45 ` Petr Baudis
2005-12-09 1:19 ` Josef Weidendorfer
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=86y82qyrqs.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=linux@horizon.com \
--cc=tihirvon@gmail.com \
--cc=torvalds@osdl.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 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.