From: Jakub Narebski <jnareb@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: F <ff.pptux@gmail.com>, git@vger.kernel.org
Subject: Re: any info getting a birdview of Git and its test suite?
Date: Mon, 19 Mar 2007 01:26:02 +0100 [thread overview]
Message-ID: <200703190126.02948.jnareb@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0703190119140.22628@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin wrote:
> On Mon, 19 Mar 2007, Jakub Narebski wrote:
>
>> First, it would be hard to work on Git in my opinion if you have no
>> experience with version control (SCM) software.
>
> I have to disagree. Git is substantially more sane than CVS, so that it is
> actually _simpler_ to learn Git than to unlearn CVS and _then_ learn Git.
Well, experience may consist of few days playing with Git. But it is not
what I wanted to say. I wanted to say that before doing any work on Git
tests one should get to know what SCM is about.
By the way, in "more extensive tests" did you want also tests of Git _API_,
and not only git commands (porcelain and plumbing)? IIRC the "more tests"
proposal for SoC2007 was by you...
(And yes, I think that Git has most sane ideas about SCM).
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2007-03-19 0:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 7:43 any info getting a birdview of Git and its test suite? F
2007-03-18 15:57 ` Brian Gernhardt
2007-03-18 23:48 ` Jakub Narebski
2007-03-19 0:20 ` Johannes Schindelin
2007-03-19 0:26 ` Jakub Narebski [this message]
2007-03-19 0:28 ` Robin Rosenberg
2007-03-19 1:31 ` Johannes Schindelin
2007-03-19 11:52 ` Andy Parkins
2007-03-19 14:18 ` Johannes Schindelin
2007-03-19 16:12 ` Nicolas Pitre
2007-03-19 17:34 ` J. Bruce Fields
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=200703190126.02948.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=ff.pptux@gmail.com \
--cc=git@vger.kernel.org \
/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).