From: "Eli Zaretskii" <eliz@gnu.org>
To: Stan Shebs <shebs@apple.com>
Cc: gdb@sources.redhat.com
Subject: Re: Unfinished projects
Date: Fri, 15 Apr 2005 08:50:00 -0000 [thread overview]
Message-ID: <01c54197$Blat.v2.4$ae3fa180@zahav.net.il> (raw)
In-Reply-To: <425EBC8F.4030405@apple.com> (message from Stan Shebs on Thu, 14 Apr 2005 11:55:11 -0700)
> Date: Thu, 14 Apr 2005 11:55:11 -0700
> From: Stan Shebs <shebs@apple.com>
>
> Andrew's sudden departure from GDB maintenance
Did he really depart? Is that departure final or just temporary, and
if the latter, for how much time?
> seems to left a
> large number of projects in mid-process; as I'm picking through
> the latest sources trying to figure out how to merge with Apple's
> bits, it's very confusing as to how the new way is supposed to
> work when it's not documented anywhere and there's maybe only
> one example of a configuration using it.
I agree with Daniel: please list the problems and issues you need to
resolve, and let's deal with them one by one.
> So my question is - what should we do about all these? Are
> some of these intrinsically impossible to complete without
> the right collection of hardware? If so, then maybe we need
> to get tougher about dropping support for some targets, or
> else abandon the projected change.
I think we need to answer these questions on the per issue basis.
> I'd like to work on updating the GDB internals manual too, for my
> own understanding if nothing else; should I describe old ways, new
> ways, or both?
Obviously, I'd be the first to applaud the documentation effort (if
you need any help, please tell). In general, I agree with Mark here:
let's document the new ways, and only mention the old ones where it's
important for those who convert from widely used old ways.
next prev parent reply other threads:[~2005-04-15 8:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 18:55 Stan Shebs
2005-04-14 19:01 ` Daniel Jacobowitz
2005-04-14 22:03 ` Stan Shebs
2005-04-14 21:49 ` Mark Kettenis
2005-04-15 1:48 ` Russell Shaw
2005-04-15 9:04 ` Eli Zaretskii
2005-04-15 8:50 ` Eli Zaretskii [this message]
2005-04-15 17:47 ` Andrew Cagney
2005-04-15 18:37 ` Stan Shebs
2005-04-15 18:52 ` Alain Magloire
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='01c54197$Blat.v2.4$ae3fa180@zahav.net.il' \
--to=eliz@gnu.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