Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@redhat.com>
To: law@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: so-thresh.exp problems
Date: Fri, 21 Dec 2001 07:36:00 -0000	[thread overview]
Message-ID: <3C2356AD.ED7A4FE5@redhat.com> (raw)
In-Reply-To: <27680.1008891105@porcupine.cygnus.com>

Jeff, I will be on vacations soon, so please consider any
changes to testsuite/gdb.hp pre-approved.  You can even re-add
yourself as a maintainer for that bit if you want (just make
an obvious patch to MAINTAINERS).

Cheers,
Fernando

law@redhat.com wrote:
> 
>   > Nobody currently maintains the gdb.hp part of the testsuite,
> It shows.  Then again, I have my reservations about the quality of the
> code when it was installed.
> 
> For example, I just had the pleasure of finding out that HP's thread tests
> all rely on a magic pre-built binary becuase they couldn't get the testfile
> to build on hpux11.  Of course we don't even have that binary and if we
> did, it'd probably be a GPL violation to distribute it.  I'll be disabling
> those tests shortly :(
> 
>   > so you
>   > can check fixes in if you want.  I am sure it will improve things.
> It can't hurt.  Particularly when it's pretty clear that nobody's built/tested
> GDB on hpux11 since Jan 2001.
> 
>   > But I don't know about gdb/somsolib.c.  As a "Past Maintainer", you are
>   > probably the closest thing we have for an HP maintainer :-)  But is not
>   > my call.
> Understood.
> jeff

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9


      reply	other threads:[~2001-12-21 15:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-20 14:28 law
2001-12-20 14:33 ` Fernando Nasser
2001-12-20 15:08   ` Kevin Buettner
2001-12-20 15:28     ` law
2001-12-20 15:33   ` law
2001-12-21  7:36     ` Fernando Nasser [this message]

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=3C2356AD.ED7A4FE5@redhat.com \
    --to=fnasser@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=law@redhat.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