All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Johan Herland <johan@herland.net>
Cc: git@vger.kernel.org, Alex Riesen <raa.lkml@gmail.com>,
	Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Subject: Re: Adding Git to Better SCM Initiative : Comparison
Date: Fri, 30 Nov 2007 02:53:54 +0100	[thread overview]
Message-ID: <200711300253.55759.jnareb@gmail.com> (raw)
In-Reply-To: <200711300226.54338.johan@herland.net>

On Fri, 30 Nov 2007, Johan Herland wrote:
> On Friday 30 November 2007, Jakub Narebski wrote:
>> On Thu, 29 Nov 2007, Alex Riesen wrote:
>>> Jakub Narebski, Thu, Nov 29, 2007 03:26:12 +0100:
>> 
>>>> +             <s id="git">
>>>> +                 Medium. There's Git User's Manual, manpages, some
>>>> +                 technical documentation and some howtos.  All
>>>> +                 documentation is also available online in HTML format;
>>>> +                 there is additional information (including beginnings
>>>> +                 of FAQ) on git wiki.
>>>> +                 Nevertheles one of complaints in surveys is insufficient
>>> 
>>> "Nevertheless" (two "s").
>>> 
>>> BTW, I wouldn't call the level of documentation "Medium" when compared
>>> to any commercial SCM. How can they earn more than "a little", when
>>> compared to any opensource program?
>> 
>> Source code is not [user level] documentation.
>> 
>> But perhaps it should be "Good" instead of "Medium", although I think
>> not "Excellent".
> 
> If we try to compare ourselves to what's closest, i.e. Mercurial, I would
> say that Git's documentation is probably on par with what Mercurial has to
> offer. Their "Documentation" entry in the comparison is as follows:
> 
> "Very good. There's an overview and tutorial on the web site, and integrated
> help for every command."
> 
> I say we go for something similar.

Well, at least according to surveys results people perceive
"The Mercurial Book" (hgbook) as better documentation than
"Git User's Manual" + tutorials. See for example frequent requests
for "The Git Book" patterned after hgbook and/or svnbook.

BTW. the list was meant to be updated by contributors who added
SCMs, but it doesn't liik lik it is...

-- 
Jakub Narebski
Poland

  reply	other threads:[~2007-11-30  1:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-28 22:39 Adding Git to Better SCM Initiative : Comparison Jakub Narebski
2007-11-29  1:48 ` Robin Rosenberg
2007-11-29  7:17   ` Jan Hudec
2007-11-29  2:26 ` Jakub Narebski
2007-11-29 20:07   ` Alex Riesen
2007-11-30  0:18     ` Jakub Narebski
2007-11-30  1:26       ` Johan Herland
2007-11-30  1:53         ` Jakub Narebski [this message]
2007-11-30  7:16       ` Alex Riesen
2007-11-30 18:34     ` Jan Hudec
2007-12-03 19:57 ` Jakub Narebski
  -- strict thread matches above, loose matches on Subject: below --
2007-12-10 12:57 Jakub Narebski
2007-12-10 13:09 ` Eyvind Bernhardsen
2007-12-10 13:20   ` Jakub Narebski
2007-12-10 14:33 ` David Kastrup
2007-12-10 14:49 ` Florian Weimer
2007-12-10 15:23   ` Johannes Schindelin
2007-12-10 15:36     ` Florian Weimer
2007-12-10 15:47   ` Jakub Narebski
2007-12-10 16:28     ` Florian Weimer
2007-12-10 16:38   ` Linus Torvalds
2007-12-10 16:50   ` Chris Shoemaker
2007-12-10 17:21     ` Jakub Narebski
     [not found] ` <200801071057.27710.shlomif@iglu.org.il>
2008-01-13  0:44   ` Jakub Narebski
2008-01-14  0:14     ` Dmitry Potapov
2008-01-14  0:31       ` Jakub Narebski
2008-01-14  6:58         ` Dmitry Potapov
2008-01-14 12:14           ` Jakub Narebski
2008-01-13 15:05 linux
2008-01-13 15:16 ` Matthieu Moy
2008-01-13 16:25   ` Jakub Narebski
2008-01-13 18:42   ` linux
2008-01-13 19:20     ` linux

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=200711300253.55759.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=johan@herland.net \
    --cc=raa.lkml@gmail.com \
    --cc=robin.rosenberg.lists@dewire.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 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.