From: Kevin Smith <yarcs@qualitycode.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: git@vger.kernel.org
Subject: Re: missing: git api, reference, user manual and mission statement
Date: Tue, 19 Apr 2005 10:10:36 -0400 [thread overview]
Message-ID: <4265115C.8090002@qualitycode.com> (raw)
In-Reply-To: <20050419135810.GA19393@elte.hu>
Ingo Molnar wrote:
> * Kevin Smith <yarcs@qualitycode.com> wrote:
>
>>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.
Absolutely! I'm totally impressed with the progress so far.
Kevin
next prev parent reply other threads:[~2005-04-19 14:06 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
2005-04-19 14:10 ` Kevin Smith [this message]
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=4265115C.8090002@qualitycode.com \
--to=yarcs@qualitycode.com \
--cc=git@vger.kernel.org \
--cc=mingo@elte.hu \
/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