From: Steffen Prohaska <prohaska@zib.de>
To: Wincent Colaiuta <win@wincent.com>
Cc: Steven Walter <stevenrwalter@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Ciprian Dorin Craciun <ciprian.craciun@gmail.com>,
Evan Carroll <me@evancarroll.com>,
git@vger.kernel.org
Subject: Re: Announcement of Git wikibook
Date: Sun, 21 Oct 2007 12:06:53 +0200 [thread overview]
Message-ID: <5541BD5F-BCFB-4D6C-BF4F-CFD29ACBC2B1@zib.de> (raw)
In-Reply-To: <F430333B-B29B-4992-9474-0E87006CBA77@wincent.com>
On Oct 21, 2007, at 11:10 AM, Wincent Colaiuta wrote:
> El 21/10/2007, a las 5:09, Steven Walter escribió:
>
>> 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.
>
> But it's not an "intro", it's a user manual. That means it's
> supposed to be a comprehensive, in-depth treatment of just about
> everything. The technical content is a good thing; it's supposed to
> be the document you turn to when you want to move beyond
> superficial use to genuine, in-depth understanding.
But it could also have introductory parts and parts decribing
specific workflows.
Something similar to svnbook or cvsbook would be perfect. I
believe a reasonable goal is that you'll get all need if you
search gitbook with google.
Steffen
prev parent reply other threads:[~2007-10-21 10:05 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
2007-10-21 9:10 ` Wincent Colaiuta
2007-10-21 10:06 ` Steffen Prohaska [this message]
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=5541BD5F-BCFB-4D6C-BF4F-CFD29ACBC2B1@zib.de \
--to=prohaska@zib.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=ciprian.craciun@gmail.com \
--cc=git@vger.kernel.org \
--cc=me@evancarroll.com \
--cc=stevenrwalter@gmail.com \
--cc=win@wincent.com \
/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).