git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: any info getting a birdview of Git and its test suite?
Date: Mon, 19 Mar 2007 00:48:37 +0100	[thread overview]
Message-ID: <etkj4l$li$1@sea.gmane.org> (raw)
In-Reply-To: 3b051c1a0703180043n1dec45by90e5cee3393d2b4d@mail.gmail.com

<opublikowany i wysłany>

F wrote:

>     I'm interested in the "More Complete Tests" project in SoC2007.
> I've used Linux for about more than one year and know basic bash
> skills. I've downloaded the source of Git and read some test scripts
> in the t directory. But I get confused.
> 
>     As said in the gitwiki page, I'm new to Git and Open Source
> Development. I just know the basic usage and cannot figure out how one
> component interacts with each other in a few days. It's hard for me to
> write a decent plan on how to impove existing test scripts and on
> writing a new one. So is there any infomation getting a birdview of
> architecture of Git and its test suite? Or the only way is to read the
> code?

First, it would be hard to work on Git in my opinion if you have no
experience with version control (SCM) software.

Second, Git comes with two tutorials (and third in the works, check
out mailing list archives; stalled), user's manual, and introduction
and tutorial to core git. It has its own homepage, and its own wiki.

Third, t/README and comments in t/test-lib.sh should help with setting
up tests for git commands behavior.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  parent reply	other threads:[~2007-03-18 23:48 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 [this message]
2007-03-19  0:20   ` Johannes Schindelin
2007-03-19  0:26     ` Jakub Narebski
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='etkj4l$li$1@sea.gmane.org' \
    --to=jnareb@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).