public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse•cz>
To: Junio C Hamano <gitster@pobox•com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx•de>,
	Scott Chacon <schacon@gmail•com>,
	git@vger•kernel.org
Subject: Re: Official Git Homepage change? Re: git-scm.com
Date: Sat, 26 Jul 2008 16:40:40 +0200	[thread overview]
Message-ID: <20080726144040.GZ32184@machine.or.cz> (raw)
In-Reply-To: <7vtzedmeqh.fsf@gitster.siamese.dyndns.org>

On Fri, Jul 25, 2008 at 09:49:42PM -0700, Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx•de> writes:
> 
> > On Fri, 25 Jul 2008, Junio C Hamano wrote:
> >
> >> It's also somewhat interesting to observe that several people I have 
> >> never heard of in the git circle are simultaneously doing new git books, 
> >> apparently never asking for much technical advice from core git people, 
> >> by the way.

  I would say we actually worked hard to make itpossible to understand
Git without being a Git contributor and knowing the code inside-out,
didn't we? So in a sense, having books about Git written by people
outside of the developer community could be considered a certain
milestone for Git usability. At least provided the books are good, and
reading the excerpts from

	http://www.pragprog.com/titles/tsgit/pragmatic-version-control-using-git

has been a little disturbing experience at times. Then again, it is an
early alpha probably far before technical editing, so it is too early
to draw conclusions. (And after doing technical editing for a very thick
Czech book on low-level Linux programming, my standards for this phase
of book development had to be... somewhat lowered. ;-)

> Oh, mine was not a criticism but was just an observation.
> 
> Maybe the folks we consider as "git community members" are either too
> narrow, or too detached from the "real user community", and it could be
> that git books are better written without us.

  The numbers in another part of the thread show something important -
GitHub is more than SIX TIMES BIGGER than repo.or.cz! How many of you
have GitHub accounts, and how many of you are actively using repo.or.cz?
:-) And GitHub is not "just" Ruby on Rails *at all*:

	http://github.com/blog/99-popular-languages

Overally, it seems that Git is getting huge traction in the web
developers community while this is something I would presume the core
Git community of kernel hackers and such is mostly unaware of (and it is
somewhat amusing contrast). Now, these are people who we will probably
never see on the mailing list, not just because they frequently don't
even know C, and don't care to, but they might have actually never used
a mailing list before! These are the people who frequently could not
care about their VCS' internals less and finding out that Git works well
enough for them is something rather satisfying for me personally.

  I don't know if this should have any immediate effect on how we
develop Git etc., but I think it is good to be aware of the fact that
silently, huge amount of "dark mass" Git projects is accumulating and
that Git is making headways in areas many of us were little aware of.

-- 
				Petr "Pasky" Baudis
As in certain cults it is possible to kill a process if you know
its true name.  -- Ken Thompson and Dennis M. Ritchie

  parent reply	other threads:[~2008-07-26 14:41 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25 17:35 git-scm.com Scott Chacon
2008-07-25 21:20 ` git-scm.com Sverre Rabbelier
2008-07-25 21:46   ` git-scm.com Scott Chacon
2008-07-25 21:36 ` git-scm.com Johan Herland
2008-07-25 21:49   ` git-scm.com Scott Chacon
2008-07-25 22:02 ` git-scm.com Stephan Beyer
2008-07-25 22:15   ` git-scm.com Scott Chacon
2008-07-25 23:47 ` git-scm.com Junio C Hamano
2008-07-26  0:59   ` git-scm.com Scott Chacon
2008-07-26 17:10     ` git-scm.com Junio C Hamano
2008-07-27  6:19       ` git-scm.com "Peter Valdemar Mørch (Lists)"
2008-07-27 11:37       ` git-scm.com Petr Baudis
2008-07-27 18:33         ` git-scm.com Junio C Hamano
2008-07-27 22:01           ` git-scm.com Junio C Hamano
2008-07-27 23:19             ` git-scm.com Martin Langhoff
2008-07-28  3:11               ` git-scm.com Tom Werner
2008-07-28 10:50                 ` git-scm.com Johannes Schindelin
2008-07-28 18:12                   ` git-scm.com Tom Werner
2008-07-31 18:39                     ` git-scm.com Jon Loeliger
2008-07-31 20:19                       ` git-scm.com Kevin Ballard
2008-07-28 21:42                   ` git-scm.com Junio C Hamano
2008-07-28 22:34                     ` git-scm.com Martin Langhoff
2008-07-28 22:39                     ` git-scm.com Pieter de Bie
2008-07-29  5:15                     ` git-scm.com Shawn O. Pearce
2008-07-26  1:38 ` git-scm.com Patrick Aljord
2008-07-26  2:28   ` git-scm.com Scott Chacon
2008-07-26  2:37     ` git-scm.com Petr Baudis
2008-07-26  2:47       ` git-scm.com david
2008-07-26  5:30         ` git-scm.com Scott Chacon
2008-07-26  5:49           ` git-scm.com Patrick Aljord
2008-07-26  8:06             ` git-scm.com Junio C Hamano
2008-07-26  6:27           ` git-scm.com david
2008-07-26 15:48           ` git-scm.com Wincent Colaiuta
2008-07-26 18:33             ` git-scm.com Scott Chacon
     [not found]               ` <alpine.DEB.1.00.0807262110140.26810@eeepc-johanness>
2008-07-26 19:13                 ` git-scm.com Scott Chacon
2008-07-26 19:20                   ` git-scm.com Johannes Schindelin
2008-07-26 19:21                     ` git-scm.com Scott Chacon
2008-07-26 23:11             ` git-scm.com Junio C Hamano
2008-07-26  2:45     ` git-scm.com Johannes Schindelin
2008-07-26  1:53 ` Official Git Homepage change? git-scm.com Petr Baudis
2008-07-26  2:09   ` Petr Baudis
2008-07-26  4:09     ` Junio C Hamano
2008-07-26  4:28       ` Johannes Schindelin
2008-07-26  4:49         ` Junio C Hamano
2008-07-26  4:54           ` Johannes Schindelin
2008-07-26 14:40           ` Petr Baudis [this message]
2008-07-26 16:37             ` Junio C Hamano
2008-07-26 16:48               ` Thomas Adam
2008-07-27 12:22               ` Petr Baudis
2008-07-27 15:53                 ` Johannes Schindelin
2008-07-27 20:12                   ` Sverre Rabbelier
2008-07-26  6:43       ` Scott Chacon
2008-07-26  7:11         ` Junio C Hamano
2008-07-26  7:27           ` Scott Chacon
2008-07-26  7:52             ` Sverre Rabbelier
2008-07-26 14:48             ` Rene Herman
2008-07-26 15:21               ` Jakub Narebski
2008-07-26 15:32                 ` Scott Chacon
2008-07-26 15:39                   ` Jakub Narebski
2008-07-26 15:15           ` Petr Baudis
2008-07-26 20:17         ` Petr Baudis
2008-07-26 20:24           ` Jakub Narebski
2008-07-26 20:32             ` Petr Baudis
2008-08-03 14:50               ` Jonas Fonseca
2008-08-03 22:00                 ` Junio C Hamano
2008-07-27 12:35       ` Petr Baudis
2008-07-26  7:07   ` Scott Chacon
2008-07-26 14:17     ` Petr Baudis
2008-07-26  2:25 ` git-scm.com Johannes Schindelin
2008-07-26  2:33   ` git-scm.com Petr Baudis
2008-07-26  2:54   ` git-scm.com Stephan Beyer
2008-07-26  3:07     ` git-scm.com Johannes Schindelin
2008-07-26  4:55       ` git-scm.com Scott Chacon
2008-07-26  7:21         ` git-scm.com Martin Langhoff
2008-07-26  8:03 ` git-scm.com Jakub Narebski
2008-07-26 13:07   ` git-scm.com Petr Baudis
2008-07-26 18:51     ` git-scm.com Junio C Hamano

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=20080726144040.GZ32184@machine.or.cz \
    --to=pasky@suse$(echo .)cz \
    --cc=Johannes.Schindelin@gmx$(echo .)de \
    --cc=git@vger$(echo .)kernel.org \
    --cc=gitster@pobox$(echo .)com \
    --cc=schacon@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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