Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gdb@sources.redhat.com
Subject: Re: [proposal] gdb/testsuite/gdb.signal
Date: Tue, 14 Sep 2004 20:47:00 -0000	[thread overview]
Message-ID: <41475869.2090003@gnu.org> (raw)
In-Reply-To: <412BE2CE.nail3MC113MZU@mindspring.com>

> Oh dear, Andrew's already opposed to this idea.  :-/
> 
> I would like to move the signals tests to a new directory, gdb.signal.
> My reasons:
> 
> . signal handling is different from basic functionality:
>   it interacts with the kernel in new ways that "basic" gdb does not
> 
> . i'm not qualified to maintain advanced signals tests,
>   so i would like to segregate the signals tests to make it easier
>   to delegate them to a different maintainer

You're more than qualified, I don't see a specialist being helpful here 
- it's the wrong skilk (and we've too many specialist already :-).  I'd 
just gather up the relevant information and assess it, drawing on the 
knowledge of GDB's community when needed.

Andrew

> So I'm making a proposal:
> 
> (1) Setup gdb.signals and mechanically move the signals files there.
>     I would do this part, to make sure the mechanical move went okay.
> 
> (2) Seek a new senior maintainer for the new gdb.signal.  I would keep
>     the maintainership until someone volunteers and is approved.
> 
> Comments?
> 
> I'm particularly interested in whether Andrew, who is writing much
> of the code, is strongly opposed, or only mildly opposed.



  reply	other threads:[~2004-09-14 20:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-25  0:52 Michael Chastain
2004-09-14 20:47 ` Andrew Cagney [this message]
2004-09-14 21:09   ` Michael Chastain

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=41475869.2090003@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=mec.gnu@mindspring.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