Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@gnu.org>
To: cagney@gnu.org
Cc: drow@false.org, gdb-patches@sources.redhat.com
Subject: Re: [COMMIT] OpenBSD/mips64 target and native support
Date: Sun, 31 Oct 2004 22:28:00 -0000	[thread overview]
Message-ID: <200410312228.i9VMSfcQ003129@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <418545F4.8060401@gnu.org> (message from Andrew Cagney on Sun, 31 Oct 2004 15:07:16 -0500)

   Date: Sun, 31 Oct 2004 15:07:16 -0500
   From: Andrew Cagney <cagney@gnu.org>

   > Scaring away contributors by making unreasonable demands isn't a
   > sensible thing to do.

   Our situtation here is identical to what we encountered with basic 
   multi-arch, the frame code, the regcace code, the function call code. 
   There, with our help and co-operation, people not just stepped up to, 
   but also exceeded the challenge.

I strongly disagree.  The shared library code touches core parts of
GDB.  There's no way an outsider is going to be able to fix that
properly, especially since changes will have to be tested on a
multitude of platforms.  There is also absolutely no visible benefit
from making the required changes.  This is something the shared
library maintainer and core maintainers have to sort out.  It's going
to take quite a bit of time to do so.

In the mean time it is unfair to contributors to simply refuse
contribution of any new code.

Mark


  reply	other threads:[~2004-10-31 22:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-23 12:16 Mark Kettenis
2004-10-25 15:24 ` Andrew Cagney
2004-10-25 15:29   ` Daniel Jacobowitz
2004-10-25 19:01     ` Andrew Cagney
2004-10-31 18:39       ` Andrew Cagney
2004-10-31 19:45         ` Mark Kettenis
2004-10-31 20:07           ` Andrew Cagney
2004-10-31 22:28             ` Mark Kettenis [this message]
2004-11-01  0:48               ` Andrew Cagney

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=200410312228.i9VMSfcQ003129@elgar.sibelius.xs4all.nl \
    --to=kettenis@gnu.org \
    --cc=cagney@gnu.org \
    --cc=drow@false.org \
    --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