Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: gdb@sourceware.org
Subject: Re: Internals manual update
Date: Sun, 22 Jun 2008 03:22:00 -0000	[thread overview]
Message-ID: <ulk0yf92h.fsf@gnu.org> (raw)
In-Reply-To: <485D83C2.6020208@earthlink.net>

> Date: Sat, 21 Jun 2008 15:42:10 -0700
> From: Stan Shebs <stanshebs@earthlink.net>
> 
> 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.

Thanks!

> Would people be content with me posting a mega-patch(es) for overall
> progress, or would they prefer individual patches for each specific
> change?

Mega-patches are okay with me, provided that the ChangeLog entries to
go with them allow to figure out which part belongs to what 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.

Agreed.  The reason the historical parts are there is that no one made
them up to date.

> In general it seems to me that the internals manual should
> correspond to current sources closely, only have the occasional
> reference to ancient history.

Right.

Thanks again for working on this.


  reply	other threads:[~2008-06-22  3:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-21 22:42 Stan Shebs
2008-06-22  3:22 ` Eli Zaretskii [this message]
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=ulk0yf92h.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=stanshebs@earthlink.net \
    /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