public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Enze Li <enze.li@hotmail.com>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org,
	enze.li@gmx.com, jbeulich@suse.com, tom@tromey.com
Subject: Re: [PATCH] bfd: add version check to makeinfo
Date: Thu, 06 Apr 2023 18:38:32 +0300	[thread overview]
Message-ID: <831qkxqavb.fsf@gnu.org> (raw)
In-Reply-To: <OS3P286MB2152C4A8835206214E019E86F0919@OS3P286MB2152.JPNP286.PROD.OUTLOOK.COM> (message from Enze Li on Thu, 06 Apr 2023 23:00:38 +0800)

> From: Enze Li <enze.li@hotmail.com>
> Cc: binutils@sourceware.org, gdb-patches@sourceware.org, enze.li@gmx.com, 
> 	jbeulich@suse.com, tom@tromey.com
> Date: Thu, 06 Apr 2023 23:00:38 +0800
> 
> On Tue, 2023-04-04 at 11:24 -0400, Eli Zaretskii wrote:
> > Some people still use makeinfo 4.x because it's at least an order of
> > magnitude faster than version 5 and later.  For such simple problems,
> > wouldn't it be better to add the missing sectioning commands, and let
> > those users of makeinfo 4.x keep using it?
> 
> Yeah, that's an easy way out.  I'll send another patch shortly.
> 
> BTW, I found the thread[1] where this was discussed a month ago and it
> seems that both approaches are possible.

I was just expressing my opinion.  I don't have the authority to make
the decision that this should be what Binutils does.

      reply	other threads:[~2023-04-06 15:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-04 15:07 Enze Li
2023-04-04 15:24 ` Eli Zaretskii
2023-04-06 15:00   ` Enze Li
2023-04-06 15:38     ` 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=831qkxqavb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=binutils@sourceware.org \
    --cc=enze.li@gmx.com \
    --cc=enze.li@hotmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jbeulich@suse.com \
    --cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).