From: Willy Tarreau <w@1wt.eu>
To: sverre@rabbelier.nl
Cc: David Howells <dhowells@redhat.com>,
Jakub Narebski <jnareb@gmail.com>,
torvalds@osdl.org, git@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Simplified GIT usage guide
Date: Fri, 19 Dec 2008 07:33:02 +0100 [thread overview]
Message-ID: <20081219063301.GA6800@1wt.eu> (raw)
In-Reply-To: <bd6139dc0812121716w73ea1145w7f870e887e00adc0@mail.gmail.com>
On Sat, Dec 13, 2008 at 02:16:34AM +0100, Sverre Rabbelier wrote:
> On Sat, Dec 13, 2008 at 02:04, David Howells <dhowells@redhat.com> wrote:
> > (3) You put some non-basic stuff in the basic section (branching - this isn't
> > ordinarily useful, IMHO), but you miss other stuff out ('git rm' for
> > example).
>
> Erm, branching is not ordinarily useful? I think you're Doing It Wrong
> (TM) then, since branching is a Big Thing (also TM) in DVC, not using
> branches would be a bit like only using the first 4 gears in a car;
> sure, it's possible, but you're missing all that extra power!
People who want to use it as a CVS replacement don't realize that they're
using branches. They work in their local "master" branch, and don't realize
that when they fetch updates, they fetch them into a different branch.
CVS people are afraid of branches, so trying to explain them how they can
do what they're used to is better than telling them they'll have to do
what they're afraid of.
I found David's howto quite understandable. I've taught Git to people who
only knew about SVN and to people who had never heard about any SCM at all. I
tried to use the same approach each time, and while I noticed that explaining
how Git works and why it works like that appeared obvious to the newbies,
it was very awkward with SVN users. I switched to something more like
David's approach for those people and it helped a lot. They have plenty
of time after that to discover the tool by themselves.
I really think that David should maintain his doc after applying a few
fixes to it, just like Jeff maintains his own. Also, having several docs
out of the tree is better for a user looking for different analysis of
the tool than having everything offered as the product's documentation,
provided the links are easy to find (might be linked to from the Git doc).
Willy
next prev parent reply other threads:[~2008-12-19 6:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 18:28 [PATCH] Simplified GIT usage guide David Howells
2008-12-12 18:53 ` Miklos Vajna
2008-12-12 18:57 ` Johannes Schindelin
2008-12-19 0:02 ` Paul E. McKenney
2008-12-19 0:28 ` Junio C Hamano
2008-12-19 1:27 ` Paul E. McKenney
2008-12-24 4:35 ` Valdis.Kletnieks
2008-12-19 2:38 ` Johannes Schindelin
2008-12-19 5:25 ` Paul E. McKenney
2008-12-12 19:02 ` David Howells
2008-12-12 19:09 ` Miklos Vajna
2008-12-13 1:12 ` David Howells
2008-12-13 3:34 ` Miklos Vajna
2008-12-12 19:12 ` David Howells
2008-12-12 19:24 ` Sverre Rabbelier
2008-12-12 19:40 ` Aidan Van Dyk
2008-12-13 23:05 ` Nick Andrew
2008-12-14 1:45 ` Ping Yin
2008-12-12 19:39 ` Jakub Narebski
2008-12-12 19:47 ` J. Bruce Fields
2008-12-13 1:03 ` J. Bruce Fields
2008-12-13 1:14 ` David Howells
2008-12-12 20:00 ` Jeff Garzik
2008-12-12 21:34 ` Chris Friesen
2008-12-13 5:59 ` Junio C Hamano
2008-12-13 23:12 ` Nick Andrew
2008-12-12 20:07 ` Nicolas Pitre
2008-12-13 0:30 ` David Howells
2008-12-13 1:04 ` David Howells
2008-12-13 1:16 ` Sverre Rabbelier
2008-12-19 6:33 ` Willy Tarreau [this message]
2008-12-13 1:22 ` Nicolas Pitre
2008-12-13 3:35 ` Junio C Hamano
2008-12-14 10:33 ` Matthieu Moy
2008-12-14 17:33 ` Marcin Slusarz
2008-12-19 0:47 ` C. Scott Ananian
2008-12-19 9:26 ` Michael J Gruber
2008-12-19 17:08 ` C. Scott Ananian
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=20081219063301.GA6800@1wt.eu \
--to=w@1wt.eu \
--cc=dhowells@redhat.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sverre@rabbelier.nl \
--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 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).