From: Eli Zaretskii <eliz@gnu.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: drow@false.org, gdb-patches@sources.redhat.com
Subject: Re: $argc variable
Date: Tue, 15 Nov 2005 12:35:00 -0000 [thread overview]
Message-ID: <u7jbaim9z.fsf@gnu.org> (raw)
In-Reply-To: <4378BB1A.9070606@st.com> (message from Andrew STUBBS on Mon, 14 Nov 2005 16:28:10 +0000)
> Date: Mon, 14 Nov 2005 16:28:10 +0000
> From: Andrew STUBBS <andrew.stubbs@st.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sources.redhat.com
>
> Daniel Jacobowitz wrote:
> > It looks OK to me. Could you post the revised documentation (to
> > gdb-patches, please) so that we can make sure that Eli and you did
> > converge? I couldn't quite follow your earlier conversation.
>
> Here is the full patch including both code and docs.
>
> In the end I have dropped the index altogether. Eli didn't like the
> kindex and the cindex would be so close to the cindex for the section,
> and so similar in content, that it would be pointless.
>
> I still think there is an argument for a kindex entry for both $argc and
> $arg0...$arg1 in case people don't know they are looking for
> 'user-defined', but I'm not really that bothered.
>
> OK?
OK for the documentation patch.
next prev parent reply other threads:[~2005-11-15 4:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <436A0BD2.5080505@st.com>
[not found] ` <20051107001800.GF19200@nevyn.them.org>
[not found] ` <436F35E9.4070808@st.com>
[not found] ` <20051107133538.GA2331@nevyn.them.org>
[not found] ` <43709E94.4070004@st.com>
[not found] ` <u7jbisp6n.fsf@gnu.org>
[not found] ` <4371D9A6.40109@st.com>
[not found] ` <u3bm5sk6i.fsf@gnu.org>
[not found] ` <43731C16.2040203@st.com>
[not found] ` <20051113173524.GC1945@nevyn.them.org>
2005-11-14 22:12 ` Andrew STUBBS
2005-11-15 12:35 ` Eli Zaretskii [this message]
2005-11-15 12:39 ` Daniel Jacobowitz
2005-11-15 17:54 ` Andrew STUBBS
2005-11-16 5:52 ` Eli Zaretskii
2005-11-16 14:43 ` Andrew STUBBS
2005-11-16 16:19 ` Daniel Jacobowitz
2005-11-16 4:01 ` 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=u7jbaim9z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.stubbs@st.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.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