Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ralf Corsepius <ralf.corsepius@rtems.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Ralf Corsepius <ralf.corsepius@rtems.org>,
	  Jan Kratochvil <jan.kratochvil@redhat.com>,
	 gdb@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: Re: GDB 6.8.92 available for testing
Date: Fri, 02 Oct 2009 02:46:00 -0000	[thread overview]
Message-ID: <4AC5695E.6040109@rtems.org> (raw)
In-Reply-To: <20091001171156.GD6532@adacore.com>

On 10/01/2009 07:11 PM, Joel Brobecker wrote:
>> You are forgetting about the 3rd parties, which apply distros as their
>> basis.
>
> Just to be clear: No one has any obligation towards you or us.

Right, but ...

My definition of a bug is "something which doesn't work as advertised"
--enable-system-readline is of this kind

> We all
> make the code available in some form, but we all have local modifications
> that we have not submitted for one reason or another.  You probably have
> your local modifications too, so why not just add Red Hat's patch in
> your list,
That's what I already did.

> and then work on helping us fixing the problem that causes
> this patch to be necessary?
I am more than willing to assist you in doing so, but this is the long 
term solution.

A short term solution is to apply one of the proposals to upstream gdb, 
even though they are "hackerish".

Being perfectionistic and forcing users to cope with known bugs isn't 
helpful to anybody. Neither to the FSF, to upstream gdb, rtems.org nor 
OS distributors nor other arbitrary users (users: here: people building 
gdb from sources).

Ralf


  reply	other threads:[~2009-10-02  2:46 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30 20:48 Joel Brobecker
2009-10-01  3:17 ` Ralf Corsepius
2009-10-01  8:59   ` Andreas Schwab
2009-10-01  9:35     ` Pierre Muller
2009-10-01  9:42       ` Andreas Schwab
2009-10-01 12:11         ` Ralf Corsepius
2009-10-01 13:10           ` Jan Kratochvil
2009-10-02 15:40             ` Tom Tromey
2009-10-02 17:26               ` Jan Kratochvil
2009-10-01 10:09   ` Jan Kratochvil
2009-10-01 11:20     ` Ralf Corsepius
2009-10-01 18:16       ` Joel Brobecker
2009-10-02  2:46         ` Ralf Corsepius [this message]
2009-10-02 15:39     ` Tom Tromey
2009-10-02 17:28       ` Jan Kratochvil
2009-10-01 17:07   ` Joel Brobecker
2009-10-01 17:21     ` Ralf Corsepius
2009-10-01 17:35       ` Mark Kettenis
2009-10-01 18:27         ` Joel Brobecker
2009-10-01 18:37           ` Mark Kettenis
2009-10-01 20:22             ` Eli Zaretskii
2009-10-01 18:40           ` Paul Pluzhnikov
2009-10-01 18:25       ` Joel Brobecker
2009-10-02 15:48       ` Tom Tromey
2009-10-02 16:57         ` Ralf Corsepius
2009-10-02 17:27           ` Tom Tromey
2009-10-02 18:04             ` Mark Kettenis
2009-10-02 18:15               ` Joel Brobecker
2009-10-02 18:24                 ` Mark Kettenis
2009-10-02 18:38                   ` Jan Kratochvil
2009-10-02 21:46                     ` Tom Tromey
2009-10-02 22:00                       ` Jan Kratochvil
2009-10-02 15:35   ` Tom Tromey
2009-10-01 12:02 ` Pierre Muller
2009-10-01 17:56   ` Joel Brobecker
2009-10-01 21:22     ` [RFA] more fixes to testsuite (was RE: GDB 6.8.92 available for testing) Pierre Muller
2009-10-01 21:28       ` Joel Brobecker

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=4AC5695E.6040109@rtems.org \
    --to=ralf.corsepius@rtems.org \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=tromey@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