unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Linas Vepstas <linasvepstas@gmail.com>
To: Paul Emsley <paul.emsley@bioch.ox.ac.uk>
Cc: guile-user@gnu.org
Subject: Re: Greg testing framework
Date: Tue, 3 Feb 2009 09:14:39 -0600	[thread overview]
Message-ID: <3ae3aa420902030714g1fd4bed1p9c99af37d8c6e491@mail.gmail.com> (raw)
In-Reply-To: <49883DE6.6090906@bioch.ox.ac.uk>

2009/2/3 Paul Emsley <paul.emsley@bioch.ox.ac.uk>:
> Ludovic Courtès wrote:
>> Paul Emsley <paul.emsley@bioch.ox.ac.uk> writes:
>>> However, Greg is great.
>>>
>>> This is Greg's Home:
>>> http://home.gna.org/greg/
>>>
>>> I made some fixes that didn't make it into stable release, I get the
>>> fixed up Greg from here:
>>>
>>> http://www.ysbl.york.ac.uk/~emsley/software/extras/greg-2.0.0-pe.tar.gz
>>>
>>
>> What's the maintainance status?  It it sill used in GNUstep or other
>> projects?  It looks much nicer than DejaGNU...
>
> I'm afraid that I can't be of much help - I don't know in what way GNUstep
> uses Greg (however, I use it almost every day).  **Maurizio Boriani is the
> maintainer (his email address is in the README file), but he **does not
> correspond with me.
>
> As for DejaGNU vs Greg... tcl vs guile?  Night and day... no contest!

Maurizio Boriani seems to have vanished somewhere.
I took over maintenance for guile-dbi from him just late
last year; I never received a response from him in
3-4 months of trying.

I eventually convinced the gna.org people to grant me
write access to the guile-dbi project, but that also was
not easy to do -- They did not respond on thier 'normal'
channels, I had to file a server bug or something else
strange like that, to get their attention.

The right thing to do would be to register with gna.org,
and try to get them to add you as a project maintainer
for greg, and push your updates there.

--linas




  reply	other threads:[~2009-02-03 15:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-01 20:35 more debugging info needed Paul Emsley
2009-02-01 21:32 ` Neil Jerram
2009-02-02  1:23   ` Paul Emsley
2009-02-02 22:05     ` Neil Jerram
2009-02-02 23:23       ` Paul Emsley
2009-02-03 11:18         ` Greg testing framework Ludovic Courtès
2009-02-03 12:51           ` Paul Emsley
2009-02-03 15:14             ` Linas Vepstas [this message]
2009-02-03 20:27         ` more debugging info needed Neil Jerram

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3ae3aa420902030714g1fd4bed1p9c99af37d8c6e491@mail.gmail.com \
    --to=linasvepstas@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=paul.emsley@bioch.ox.ac.uk \
    /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).