From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Document breakage of Solaris Thread Debugging
Date: Wed, 12 Jul 2006 21:17:00 -0000 [thread overview]
Message-ID: <20060712211724.GV24622@nevyn.them.org> (raw)
In-Reply-To: <20060621045703.GB976@adacore.com>
On Tue, Jun 20, 2006 at 09:57:03PM -0700, Joel Brobecker wrote:
> Hello,
>
> Following the creation of threads/2137, I propose the following addition
> to the PROBLEMS file. It's a bit terse, but I don't know more details of
> the problem.
>
> 2006-06-20 Joel Brobecker <brobecker@adacore.com>
>
> * PROBLEMS: Document threads/2137.
>
> OK to apply?
With the 6.6 -> 6.5 correction this patch is fine.
I think this is another one of those files where you should feel free
to check in patches yourself; the release manager ought to be able to
document issues with the release!
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-07-12 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 4:57 Joel Brobecker
2006-06-21 5:00 ` Joel Brobecker
2006-06-21 17:18 ` Eli Zaretskii
2006-06-23 3:02 ` Joel Brobecker
2006-07-12 21:17 ` Daniel Jacobowitz [this message]
2006-07-14 22:56 ` 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=20060712211724.GV24622@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--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