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>,
	gdb@sourceware.org,   Jan Kratochvil <jan.kratochvil@redhat.com>,
	 Tom Tromey <tromey@redhat.com>
Subject: Re: GDB 6.8.92 available for testing
Date: Thu, 01 Oct 2009 17:21:00 -0000	[thread overview]
Message-ID: <4AC4E4F6.5080500@rtems.org> (raw)
In-Reply-To: <20091001170744.GC6532@adacore.com>

On 10/01/2009 07:07 PM, Joel Brobecker wrote:
>> None of the patches I had submitted to gdb-patches had been applied.
>
> I am not aware of any patch from you that is still pending.
> I remember one patch about a warning on Solaris that was rejected
> because it turned out the warning was a GCC bug.
>
> Regardless of the specific situation, submitting patches does not
> mean that they will be applied, neither in the HEAD nor the branch.
> If they had been applied, you would have known because, either:
> you checked the patch in for you; or you asked someone else to do it,
> at which point the commit would have been confirmed to you and the
> gdb-patches list.
>

Eg. this one:
http://sourceware.org/ml/gdb-patches/2009-09/msg00585.html

and this one:
http://sourceware.org/ml/gdb-patches/2009-09/msg00556.html

But I presume, I can consider the later one to be rejected - This 
doesn't help anybody, but ... you want it this way, so be it.

Ralf


  reply	other threads:[~2009-10-01 17:21 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
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 [this message]
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=4AC4E4F6.5080500@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