From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: GDB in C++
Date: Thu, 12 Jul 2007 03:16:00 -0000 [thread overview]
Message-ID: <umyy29urv.fsf@gnu.org> (raw)
In-Reply-To: <20070711213153.GA3615@caradoc.them.org> (message from Daniel Jacobowitz on Wed, 11 Jul 2007 17:31:53 -0400)
> Date: Wed, 11 Jul 2007 17:31:53 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> On Wed, Jul 11, 2007 at 01:41:11PM -0700, Jim Blandy wrote:
> > I wouldn't object to moving the internals documentation there.
> > High-level organization is pretty key to effective documentation,
> > though, so the wiki would need aggressive gardening. It would
> > probably be good for it to have an appointed editor, to avoid ending
> > up with two or three competing theories for the overall organization.
>
> For the record, I would object. I think the internals manual is fine
> where it is, and would be no more likely to be expanded and kept up to
> date if it were moved.
Agreed.
next prev parent reply other threads:[~2007-07-12 3:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 14:56 Michael Eager
2007-07-01 20:54 ` Daniel Jacobowitz
2007-07-02 1:33 ` Joel Brobecker
2007-07-03 3:49 ` Michael Eager
2007-07-03 7:55 ` Mark Kettenis
2007-07-11 21:04 ` Jan Kratochvil
2007-07-02 7:21 ` Mark Kettenis
2007-07-03 3:57 ` Michael Eager
2007-07-03 7:03 ` Fabian Cenedese
2007-07-03 12:14 ` Robert Dewar
2007-07-03 19:09 ` Gary Funck
2007-07-11 19:47 ` Thiago Jung Bauermann
2007-07-11 19:59 ` Paul Koning
2007-07-11 20:41 ` Jim Blandy
2007-07-11 21:00 ` Gary Funck
2007-07-11 21:32 ` Daniel Jacobowitz
2007-07-11 21:38 ` Robert Dewar
2007-07-12 3:16 ` Eli Zaretskii [this message]
2007-07-12 2:24 ` Michael Eager
2007-07-13 20:21 ` Thiago Jung Bauermann
2007-07-13 20:55 ` Eli Zaretskii
2007-07-13 21:24 ` Thiago Jung Bauermann
2007-07-12 3:11 ` Eli Zaretskii
2007-07-11 21:11 ` Gary Funck
2007-07-02 20:21 ` David Daney
2007-07-02 20:28 ` 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=umyy29urv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--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