From: "Eli Zaretskii" <eliz@elta.co.il>
To: bje@wasabisystems.com
Cc: gdb@sources.redhat.com
Subject: Re: makeinfo with gdb.texinfo
Date: Thu, 03 Apr 2003 02:57:00 -0000 [thread overview]
Message-ID: <1659-Thu03Apr2003055028+0300-eliz@elta.co.il> (raw)
In-Reply-To: <3E8ACD85.7060900@wasabisystems.com> (message from Ben Elliston on Wed, 02 Apr 2003 21:46:13 +1000)
> Date: Wed, 02 Apr 2003 21:46:13 +1000
> From: Ben Elliston <bje@wasabisystems.com>
>
> In the case of Info, the behaviour you describe creates, in
> practice, more problems than it solves.
Obviously, I disagree, but you are welcome to post this on bug-texinfo
mailing list, where the Texinfo maintainers will see it.
prev parent reply other threads:[~2003-04-03 2:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 17:22 Bob Rossi
2003-03-31 17:42 ` Daniel Jacobowitz
2003-03-31 17:52 ` Bob Rossi
2003-03-31 18:12 ` Doug Evans
2003-03-31 18:22 ` Bob Rossi
2003-04-02 1:00 ` Ben Elliston
2003-04-02 3:25 ` Eli Zaretskii
2003-04-02 11:46 ` Ben Elliston
2003-04-02 13:10 ` Andreas Schwab
2003-04-02 15:48 ` Andrew Cagney
2003-04-03 2:57 ` Eli Zaretskii [this message]
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=1659-Thu03Apr2003055028+0300-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=bje@wasabisystems.com \
--cc=gdb@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