Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
	gdb-patches@sources.redhat.com, kettenis@gnu.org
Subject: Re: RFC: patch to lin-lwp.c
Date: Wed, 08 Oct 2003 17:57:00 -0000	[thread overview]
Message-ID: <3F84500A.30405@redhat.com> (raw)
In-Reply-To: <3F83582B.1060408@redhat.com>


>> If not, I'd like to clearly indicate who can approve patches
> to lin-lwp.c.
> 
> It's more who ought to than who can.  I think any of you, me,
> Mark, or Jim Blandy (and maybe we ought to add Jeff Johnston)
> are qualified to approve them, but I don't know which one or
> two persons understand it fully enough to be called on as a
> maintainer.  Jim and I, for instance, worked on it a long time
> ago.
> 
> Part of the problem, I think, is that nobody really wants it.
> It's complicated, difficult, and fragile.

The general trend for such code to not have an explicit maintainer. 
Instead changes get approved using peer-review that involves at least 
one core maintainer.  Anything architectural being pulled out and 
discssed separatly.

I should also red flag that changing the target vector means changing 
the thread code so "it could be fun times".

enjoy,
Andrew



  reply	other threads:[~2003-10-08 17:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-05 23:22 J. Johnston
2003-08-06 17:11 ` J. Johnston
2003-10-04 21:41   ` Daniel Jacobowitz
2003-10-08  0:19     ` Michael Snyder
2003-10-08 17:57       ` Andrew Cagney [this message]
2003-10-08 18:00   ` Daniel Jacobowitz
2003-10-08 20:07     ` J. Johnston

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=3F84500A.30405@redhat.com \
    --to=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@gnu.org \
    --cc=msnyder@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