From: Stan Shebs <stanshebs@earthlink.net>
To: gdb@sourceware.org
Subject: Internals manual update
Date: Sat, 21 Jun 2008 22:42:00 -0000 [thread overview]
Message-ID: <485D83C2.6020208@earthlink.net> (raw)
So as I've been refreshing my memory about GDB code, I've also been
going through the internals manual and making it be more consistent with
the current state of things. Would people be content with me posting a
mega-patch(es) for overall progress, or would they prefer individual
patches for each specific change?
Also, one specific change I made was to whack down the host stuff to
basically one line that says "we used to have host config files",
instead of a full section with a warning at the top that the material is
of historical interest only. My thought is that if someone really wanted
to research a long-gone macro more thoroughly than just review of
ChangeLog entries, they would want to get old releases anyway, which
would have both internals manual and sources using that macro. In
general it seems to me that the internals manual should correspond to
current sources closely, only have the occasional reference to ancient
history.
Stan
next reply other threads:[~2008-06-21 22:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 22:42 Stan Shebs [this message]
2008-06-22 3:22 ` Eli Zaretskii
2008-06-22 4:19 ` Daniel Jacobowitz
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=485D83C2.6020208@earthlink.net \
--to=stanshebs@earthlink.net \
--cc=gdb@sourceware.org \
/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