From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>, Carl Bordum Hansen <carl@bordum.dk>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] etc/texi2pod.pl: convert @t{} to C<>
Date: Tue, 17 Sep 2019 19:03:00 -0000 [thread overview]
Message-ID: <b60d1647-fb4f-0fcb-7da5-f62e0130779a@simark.ca> (raw)
In-Reply-To: <87lfumwz5h.fsf@tromey.com>
On 2019-09-17 2:33 p.m., Tom Tromey wrote:
>>>>>> "Carl" == Carl Bordum Hansen <carl@bordum.dk> writes:
>
> Carl> Both are intended to be stylized in a typewriter font.
>
> Thank you for doing this.
>
> This seems fine but I wonder if we should simply copy the entire script
> from gcc, and move it to contrib/ as well to further parallel gcc.
> Would there be a drawback to doing this?
>
> Carl> etc/texi2pod.pl | 2 +-
> Carl> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> This needs a ChangeLog entry regardless.
>
> Tom
Hi Tom,
I don't know if you said this before of after seeing the patch I proposed here:
https://sourceware.org/ml/gdb-patches/2019-09/msg00305.html
Ideally we'd have the exact same version as gcc. But I chose not to blindly copy the
gcc version, because it causes other changes to the generated files, and I don't know
if they are desirable or not. Also, there are some changes local to binutils-gdb that
should be either removed if no longer useful, or ported over to gcc. In the interest
of fixing the reported issue without opening a pandora's box, I opted for the smallest
fix possible (which is still a small step towards syncing both versions).
Simon
next prev parent reply other threads:[~2019-09-17 19:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 22:04 Carl Bordum Hansen
2019-09-17 1:40 ` Simon Marchi
2019-09-17 3:22 ` Simon Marchi
2019-09-17 18:33 ` Tom Tromey
2019-09-17 19:03 ` Simon Marchi [this message]
2019-09-17 19:22 ` Tom Tromey
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=b60d1647-fb4f-0fcb-7da5-f62e0130779a@simark.ca \
--to=simark@simark.ca \
--cc=carl@bordum.dk \
--cc=gdb-patches@sourceware.org \
--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