From: "Eli Zaretskii" <eliz@gnu.org>
To: karl@freefriends.org (Karl Berry)
Cc: cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: @dircategory for gdb manuals
Date: Fri, 28 May 2004 08:30:00 -0000 [thread overview]
Message-ID: <9003-Fri28May2004104225+0300-eliz@gnu.org> (raw)
In-Reply-To: <200405271341.i4RDfa025333@f7.net>
> Date: Thu, 27 May 2004 09:41:36 -0400
> From: karl@freefriends.org (Karl Berry)
>
> > Perhaps "Software development" would be better.
>
> Why not leave it in the same category as the GDB user manual?
>
> "Software development" is in fact the category I was proposing for the
> GDB user manual.
That's okay with me.
> I doubt that some J. Random Hacker will be too interested in reading
> that, unless he or she is working on GDB development.
>
> I don't understand what you're saying. I agree, J. Random Hacker is not
> likely to be interested in reading the GDB internals manual unless
> they're working on GDB. And this is why I proposed different categories
> for them!
I was saying that gdbint.texinfo without gdb.texinfo is not a useful
reading. They should be (and probably are) read together, and thus
it doesn't make much sense, IMHO, to separate them.
> Since stabs, bfd, and mmalloc are pretty clearly "Software libraries",
> it seemed to me that the most natural place for the internals manual
> (which is related to those) was also Software libraries
The difference between bfd and mmalloc on the one side, and stabs on
the other is that the latter is not really a general-purpose library
like the former.
next parent reply other threads:[~2004-05-28 8:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200405271341.i4RDfa025333@f7.net>
2004-05-28 8:30 ` Eli Zaretskii [this message]
[not found] <200405281324.i4SDOeS10812@f7.net>
2004-05-29 11:16 ` Eli Zaretskii
2004-05-31 19:21 ` Andrew Cagney
2004-06-01 4:24 ` Eli Zaretskii
[not found] <200405261326.i4QDQTd11571@f7.net>
2004-05-27 7:15 ` Eli Zaretskii
[not found] <200404101902.i3AJ2UD13760@tug.org>
2004-05-25 21:27 ` Andrew Cagney
2004-05-26 10:02 ` Eli Zaretskii
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=9003-Fri28May2004104225+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=karl@freefriends.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