From: Daniel Jacobowitz <drow@false.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH]: Fix thread debugging on Sparc/Linux
Date: Tue, 04 Apr 2006 22:14:00 -0000 [thread overview]
Message-ID: <20060404221448.GA12279@nevyn.them.org> (raw)
In-Reply-To: <20060404.150859.58684361.davem@davemloft.net>
On Tue, Apr 04, 2006 at 03:08:59PM -0700, David S. Miller wrote:
> > Thanks. But, in the future, could you please wait for your patches to
> > be reviewed like everyone else (or ask to be the maintainer for this
> > port)?
>
> There is no maintainer for this port, I'm pretty much the only
> person who works on it actively. :)
I realize that, and I'm glad you do - Debian users still use it for
sure. I have a couple other SPARC-specific bugs I need to get back to.
But I just spent months of my life getting the GDB developers to agree
to a set of policies, and eventually succeeded. I'd really appreciate
it if you could follow them if you intend to contribute to GDB.
They're documented in gdb/MAINTAINERS and were announced on the GDB
lists.
> > You added includes to source files, so Makefile.in needs to be updated.
>
> I'll fix that up, thanks for mentioning.
Thanks.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-04 22:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-02 7:12 David S. Miller
2006-04-04 21:54 ` David S. Miller
2006-04-04 22:06 ` Daniel Jacobowitz
2006-04-04 22:08 ` David S. Miller
2006-04-04 22:14 ` Daniel Jacobowitz [this message]
2006-04-04 22:22 ` David S. Miller
2006-04-04 22:43 ` Daniel Jacobowitz
2006-04-04 22:54 ` David S. Miller
2006-04-04 23:11 ` Daniel Jacobowitz
2006-04-04 23:12 ` David S. Miller
2006-04-04 23:52 ` David S. Miller
2006-04-04 23:58 ` Michael Snyder
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=20060404221448.GA12279@nevyn.them.org \
--to=drow@false.org \
--cc=davem@davemloft.net \
--cc=gdb-patches@sources.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