From: Tom Tromey <tom@tromey.com>
To: "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 18:33:00 -0000 [thread overview]
Message-ID: <87lfumwz5h.fsf@tromey.com> (raw)
In-Reply-To: <BX1RMFNHD09K.2UR7RI8XL51IC@carl-T440p> (Carl Bordum Hansen's message of "Tue, 17 Sep 2019 00:04:18 +0200")
>>>>> "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
next prev parent reply other threads:[~2019-09-17 18:33 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 [this message]
2019-09-17 19:03 ` Simon Marchi
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=87lfumwz5h.fsf@tromey.com \
--to=tom@tromey.com \
--cc=carl@bordum.dk \
--cc=gdb-patches@sourceware.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