From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>,
gdb-patches <gdb-patches@sourceware.org>,
Stan Shebs <stan@codesourcery.com>
Subject: gdb.texinfo is getting too big
Date: Mon, 14 Oct 2013 20:06:00 -0000 [thread overview]
Message-ID: <CADPb22S7Yjz=um_7P_9M_yS-ko7+jNQXzf8HqtWn3QdWqoD2DA@mail.gmail.com> (raw)
Hi.
What do people think about splitting up gdb.texinfo?
I don't have a strong preference regarding how, I just know it'd be
easier for me to work with if topics like the python scripting were in
their own file.
Stan reminded me that gcc docs are split up.
Something like splitting the gdb docs up per chapter would "work for me".
[The result would still be *one* manual, but editing and maintaining
it would, for me,
be easier.]
Thoughts? Suggestions?
next reply other threads:[~2013-10-14 20:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 20:06 Doug Evans [this message]
2013-10-14 20:10 ` Eli Zaretskii
2013-10-14 20:26 ` Doug Evans
2013-10-15 2:44 ` Eli Zaretskii
2013-10-16 18:55 ` Doug Evans
2013-10-16 19:01 ` Eli Zaretskii
2013-10-16 19:52 ` Pedro Alves
2013-10-16 20:06 ` Eli Zaretskii
2013-10-16 20:10 ` Paul_Koning
2013-10-16 21:41 ` Pedro Alves
2013-11-01 19:37 ` Doug Evans
2013-11-01 19:57 ` Eli Zaretskii
2013-10-16 21:29 ` Pedro Alves
2013-10-16 20:07 ` 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='CADPb22S7Yjz=um_7P_9M_yS-ko7+jNQXzf8HqtWn3QdWqoD2DA@mail.gmail.com' \
--to=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=stan@codesourcery.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