public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Anthony Green <green@cygnus.com>
To: abies@pg.gda.pl
Cc: mauve-discuss@sourceware.cygnus.com
Subject: Re: BitSet test
Date: Thu, 01 Apr 1999 00:00:00 -0000	[thread overview]
Message-ID: <199902031724.JAA27147@hoser.cygnus.com> (raw)
Message-ID: <19990401000000.2tdJBHbuXfgKO7zh-vInd03fwSspP1whlEsaX4Y0WQQ@z> (raw)
In-Reply-To: <36B85E1C.6C8D389A@pg.gda.pl>

Artur wrote:
> Attached is test for JDK1.0 BitSet. 

Cool - thanks.

> BTW, mauve check rules are very counter-intuitive for me. I was
> supposing that with
> make KEYS='!java java.util.BitSet' check
> I'll be able to run only my test. Actual result was to run all tests. I
> was trying to give these options in mauve-something file, no luck. I've
> ended up with compiling by hand and running through make check with hand
> edited 'classes' file

The following works..

make KEYS='!java. java.util.BitSet' check

Note the extra '.'.

> // Taqs: JDK1.0

This would have to be "Tags" :-)

I think we will have to start requiring copyright notices in the test
files.  Artur, do you mind if I add the following header to your test
file before I check it in?

/* Copyright (C) 1999 Artur Biesiadowski

   This file is part of Mauve.

   Mauve is free software; you can redistribute it and/or modify
   it under the terms of the GNU General Public License as published by
   the Free Software Foundation; either version 2, or (at your option)
   any later version.

   Mauve is distributed in the hope that it will be useful,
   but WITHOUT ANY WARRANTY; without even the implied warranty of
   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
   GNU General Public License for more details.

   You should have received a copy of the GNU General Public License
   along with Mauve; see the file COPYING.  If not, write to
   the Free Software Foundation, 59 Temple Place - Suite 330,
   Boston, MA 02111-1307, USA.  */


AG

-- 
Anthony Green                                               Cygnus Solutions
                                                       Sunnyvale, California

  reply	other threads:[~1999-04-01  0:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-03  6:43 Artur Biesiadowski
     [not found] ` < 36B85E1C.6C8D389A@pg.gda.pl >
1999-02-03  9:24   ` Anthony Green [this message]
1999-04-01  0:00     ` Anthony Green
1999-04-01  0:00 ` Artur Biesiadowski
1999-02-03  6:59 Aaron M. Renn
1999-02-09 13:36 ` Tom Tromey
1999-04-01  0:00   ` Tom Tromey
1999-04-01  0:00 ` Aaron M. Renn
1999-02-09 14:17 Aaron M. Renn
1999-02-11 11:25 ` Tom Tromey
1999-04-01  0:00   ` Tom Tromey
1999-04-01  0:00 ` Aaron M. Renn

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=199902031724.JAA27147@hoser.cygnus.com \
    --to=green@cygnus.com \
    --cc=abies@pg.gda.pl \
    --cc=mauve-discuss@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).