From: Daniel Jacobowitz <drow@false.org>
To: Stan Shebs <shebs@apple.com>
Cc: gdb@sources.redhat.com
Subject: Re: Open projects list
Date: Fri, 07 Oct 2005 19:30:00 -0000 [thread overview]
Message-ID: <20051007193012.GA31596@nevyn.them.org> (raw)
In-Reply-To: <4346CB8C.10800@apple.com>
On Fri, Oct 07, 2005 at 12:25:00PM -0700, Stan Shebs wrote:
> I was poking around to see if named threads was written down anywhere
> as a desired GDB feature, and couldn't find it on web pages or in
> sources, which makes me wonder how many other longstanding wishlist
> items aren't known about. I see that there are lots of feature
> requests in bugzilla, but they are more about specific details,
> rather than overall direction, and IMHO the bugzilla format is not
> so helpful for larger or architectural changes that may need lengthy
> background and explanation, like MI levels to support, reverse
> execution infrastructure, native tracepoints, etc. GCC has a
> whole collection of pages under http://gcc.gnu.org/projects/ for
> this kind of thing.
>
> Does anybody else think we need something like this?
If we want something like this, a Wiki would be a better choice. GCC
certainly found their wiki to be more effective than the projects
pages, which are mostly translations of old projects from the source
distribution.
Also, I find it somewhat ironic that you said "in bugzilla" since we're
still living in the dark ages of gnats. I'm torn between setting up a
third independent bugzilla instance on sourceware, or going through the
pain of renumbering all the active references to PRs in the testsuite.
Open to suggestions.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-10-07 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 19:25 Stan Shebs
2005-10-07 19:27 ` Bob Rossi
2005-10-07 19:30 ` Daniel Jacobowitz [this message]
2005-10-07 19:42 ` Stan Shebs
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=20051007193012.GA31596@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=shebs@apple.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).