Git development
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Kevin Smith <yarcs@qualitycode.com>
Cc: Klaus Robert Suetterlin <robert@mpe.mpg.de>, git@vger.kernel.org
Subject: Re: missing: git api, reference, user manual and mission statement
Date: Tue, 19 Apr 2005 15:58:10 +0200	[thread overview]
Message-ID: <20050419135810.GA19393@elte.hu> (raw)
In-Reply-To: <42650CFC.1010400@qualitycode.com>


* Kevin Smith <yarcs@qualitycode.com> wrote:

> Klaus Robert Suetterlin wrote:
> > 1) There is no clear (e.g. by name) distinction between ``git as done
> > by Linus'', which is a kind of content addressable database with added
> > semantics, and ``git as done by the rest of You'', which is a kind of
> > SCM on top of Linuses stuff.
> 
> I also see this as one of the biggest obstacles right now. It would be 
> very helpful if we could achieve the clear separation between git and 
> non-git that has been part of the design since the beginning.
> 
> Git is very immature, and currently should only be used by brave 
> pioneers. About the only way for a mortal to even try git is to stick 
> to git-pasky releases, and not try to track all the patches flying 
> around.

hey, it's a 2 weeks old project, but it's certainly one of the 
fastest-growing projects i've ever seen: it has so much steam that it's 
scary :) It seems that a true emergency focused a massive, spontaneous 
concentration of OSS development power.

	Ingo

  reply	other threads:[~2005-04-19 13:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19 12:36 missing: git api, reference, user manual and mission statement Klaus Robert Suetterlin
2005-04-19 13:51 ` Kevin Smith
2005-04-19 13:58   ` Ingo Molnar [this message]
2005-04-19 14:10     ` Kevin Smith
2005-04-19 16:58 ` Petr Baudis
2005-04-20 17:15   ` Andrew Timberlake-Newell

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=20050419135810.GA19393@elte.hu \
    --to=mingo@elte.hu \
    --cc=git@vger.kernel.org \
    --cc=robert@mpe.mpg.de \
    --cc=yarcs@qualitycode.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