git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Walter <stevenrwalter@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Ciprian Dorin Craciun <ciprian.craciun@gmail.com>,
	Steffen Prohaska <prohaska@zib.de>,
	Evan Carroll <me@evancarroll.com>,
	git@vger.kernel.org
Subject: Re: Announcement of Git wikibook
Date: Sat, 20 Oct 2007 23:09:27 -0400	[thread overview]
Message-ID: <20071021030927.GA19450@dervierte> (raw)
In-Reply-To: <Pine.LNX.4.64.0710202232280.25221@racer.site>

[-- Attachment #1: Type: text/plain, Size: 1577 bytes --]

On Sat, Oct 20, 2007 at 10:34:34PM +0100, Johannes Schindelin wrote:
> I am torn.  On one side I like the Wiki approach.  On the other hand, the 
> Wiki will get less review by git oldtimers, whereas the patches to 
> user-manual are usually reviewed as thoroughly as the code patches.

No offense, but review by old timers can be both a blessing and a curse.
Well, it's not the "review" that is so much a problem as the "editorial
control."  In my opinion (and I believe this is what the original poster
was saying), the official Git User Manual focuses more on technical
issues and less on introducing git to a new user.

This makes perfect sense given that it's edited by oldtimers, who are
neither inclined nor particularly suited to explaining git to newbies;
they have simply forgotten what it was like for these concepts to be
foreign.  They eat SHA1 hashes for breakfast and dream about index
files.  And that's great :)

I don't think the wikibook should try to duplicate the Git User Manual.
That would be a wasted effort.  But there is a niche to be filled in git
documentation, particularly in regard to specific workflows and git best
practices.  With git, TMTOWTDI.  It's quite difficult for a newbie to
know which of those ways will come back and bite them in the ass down the
road.

Of course, it is a wikibook, so it will go where it goes.  I for one am
glad to see this project started.
-- 
-Steven Walter <stevenrwalter@gmail.com>
Freedom is the freedom to say that 2 + 2 = 4
B2F1 0ECC E605 7321 E818  7A65 FC81 9777 DC28 9E8F 

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-10-21  3:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19 20:21 Announcement of Git wikibook Evan Carroll
2007-10-19 20:58 ` Steffen Prohaska
2007-10-20  7:40   ` Ciprian Dorin Craciun
2007-10-20 11:20     ` Wincent Colaiuta
2007-10-20 21:34     ` Johannes Schindelin
2007-10-21  3:09       ` Steven Walter [this message]
2007-10-21  9:10         ` Wincent Colaiuta
2007-10-21 10:06           ` Steffen Prohaska

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=20071021030927.GA19450@dervierte \
    --to=stevenrwalter@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=ciprian.craciun@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=me@evancarroll.com \
    --cc=prohaska@zib.de \
    /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).