git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Wielemaker <wielemak@science.uva.nl>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Jan Wielemaker <jan@swi-prolog.org>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git-cvsserver: added support for update -p
Date: Wed, 10 Oct 2007 19:27:38 +0200	[thread overview]
Message-ID: <200710101927.38949.wielemak@science.uva.nl> (raw)
In-Reply-To: <Pine.LNX.4.64.0710101740400.4174@racer.site>

> On Wed, 10 Oct 2007, Jan Wielemaker wrote:
> > Is there a test suite for git-cvsserver?
>
> Yes: t/t9400-git-cvsserver-server.sh

Thanks.  B.t.w. from the main directory:

gollem (git) 21_> make check
for i in *.c; do 
sparse -g -O2 -Wall  -DSHA1_HEADER='<openssl/sha.h>' -DETC_GITCONFIG='"/home/jan/etc/gitconfig"' -DNO_STRLCPY -D__BIG_ENDIAN__ -D__powerpc__ 
$i || exit; done
/bin/sh: sparse: command not found
make: *** [check] Error 127

Dunno, but maybe something like this is more appropriate:

	echo "See t/README for testing GIT"

	Cheers --- Jan

P.s.	My modified version passes all tests.

  reply	other threads:[~2007-10-10 17:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-10 11:16 [PATCH] git-cvsserver: added support for update -p Jan Wielemaker
2007-10-10 13:47 ` Johannes Schindelin
2007-10-10 14:26   ` Jan Wielemaker
2007-10-10 16:41     ` Johannes Schindelin
2007-10-10 17:27       ` Jan Wielemaker [this message]
2007-10-10 19:27         ` Johannes Schindelin
2007-10-10 20:00 ` Frank Lichtenheld
2007-10-11  8:45   ` Andreas Ericsson
2007-10-11 16:36 ` [PATCH] cvsserver: " Frank Lichtenheld
2007-10-11 16:52   ` Jan Wielemaker
2007-10-11 17:29     ` Frank Lichtenheld
2007-10-11 20:59   ` Johannes Schindelin
2007-10-11 21:07     ` Frank Lichtenheld

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=200710101927.38949.wielemak@science.uva.nl \
    --to=wielemak@science.uva.nl \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jan@swi-prolog.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).