Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: drow@false.org
Cc: gdb-patches@sourceware.org
Subject: Re: [v850 sim] correcting psw flags for divide special cases.
Date: Tue, 18 Apr 2006 19:36:00 -0000	[thread overview]
Message-ID: <200604181936.k3IJa7m0004548@greed.delorie.com> (raw)
In-Reply-To: <20060418192447.GB14876@nevyn.them.org> (message from Daniel 	Jacobowitz on Tue, 18 Apr 2006 15:24:47 -0400)


> Yes, but I have to go back two and a half years to find the last
> patch that wasn't related to build machinery :-)

Nobody said support was pretty.

> How about if we extended the Authorized Committer blurb from
> gdb/MAINTAINERS into sim/?

That would probably be reasonable.  It's not my ability I'm concerned
about, it's available time, so being able to commit patches without
misleading impressions of copious available resources would be
acceptable.

There's probably a number of people in my position, who occasionally
do support outside of their mainstream maintainerships, and have
enough expertise to do so independently, but not enough time to commit
to a maintainership.  A consistent solution to this would be
worthwhile.


  reply	other threads:[~2006-04-18 19:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-13 23:37 DJ Delorie
2006-04-14 20:35 ` Daniel Jacobowitz
2006-04-14 20:36   ` Daniel Jacobowitz
2006-04-17 19:35   ` DJ Delorie
2006-04-17 19:49     ` Daniel Jacobowitz
2006-04-17 20:20       ` DJ Delorie
2006-04-18 19:25         ` Daniel Jacobowitz
2006-04-18 19:36           ` DJ Delorie [this message]
2006-04-20 13:09             ` Daniel Jacobowitz
2006-05-04 15:40               ` Daniel Jacobowitz
2006-04-18 19:44 ` [v850 sim] REVISED " DJ Delorie

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=200604181936.k3IJa7m0004548@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    /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