From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches <gdb-patches@sourceware.org>,
Stan Shebs <stan@codesourcery.com>
Subject: Re: gdb.texinfo is getting too big
Date: Wed, 16 Oct 2013 18:55:00 -0000 [thread overview]
Message-ID: <CADPb22QOG=kH_HPr59rEZEQPhQh0QS_JYi82W-McmfLf+fifCA@mail.gmail.com> (raw)
In-Reply-To: <83mwmbp80v.fsf@gnu.org>
On Mon, Oct 14, 2013 at 7:44 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Mon, 14 Oct 2013 13:25:59 -0700
>> From: Doug Evans <dje@google.com>
>> Cc: gdb-patches <gdb-patches@sourceware.org>, Stan Shebs <stan@codesourcery.com>
>>
>> Next question: Any strong preference for how?
>> I suggested splitting up by chapter, and that's fine with me, but
>> before I do all that work, IWBN to get pre-approval for at least the
>> general idea.
>> I count > 40.
>> Is there a less granular split people want?
>
> No, it's too fine-grained. 40 files is too much, IMO. It is better
> to group several consecutive chapters into a single file.
>
>> [Keeping the split mechanical, by something like chapter, is easy.
>> Otherwise a discussion could drag on ...]
>
> Well, you started it ;-)
The worry I have with any kind of grouping not based on the doc itself
is that it introduces a potentially non-intuitive layer that someone
has to learn in order to know which file contains the text one wants
to edit. grep will find it of course, but if one is having to grep
too much, would that be a problem?
next prev parent reply other threads:[~2013-10-16 18:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 20:06 Doug Evans
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 [this message]
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='CADPb22QOG=kH_HPr59rEZEQPhQh0QS_JYi82W-McmfLf+fifCA@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