From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: tromey@redhat.com
Cc: palves@redhat.com, binutils@sourceware.org, gdb@sourceware.org
Subject: Re: File missing from the git: texinfo/texinfo.tex
Date: Thu, 24 Oct 2013 15:50:00 -0000 [thread overview]
Message-ID: <201310241547.r9OFlwZ3017071@ignucius.se.axis.com> (raw)
In-Reply-To: <87li1ibwwh.fsf@fleche.redhat.com> (message from Tom Tromey on Thu, 24 Oct 2013 15:50:38 +0200)
> From: Tom Tromey <tromey@redhat.com>
> Date: Thu, 24 Oct 2013 15:50:38 +0200
> Pedro> Yeah. If it were up to me, I'd just bite the bullet and do
> Pedro> this.
>
> I restarted the conversion here, with the texinfo bug fixed.
FWIW, I noticed no other issues while working around the texinfo
issue.
brgds, H-P
prev parent reply other threads:[~2013-10-24 15:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 16:40 Hans-Peter Nilsson
2013-10-23 16:51 ` Tom Tromey
2013-10-23 16:55 ` Fred Cooke
2013-10-23 17:05 ` Tom Tromey
2013-10-23 17:00 ` Paul Smith
2013-10-23 17:04 ` Hans-Peter Nilsson
2013-10-24 9:56 ` Pedro Alves
2013-10-24 11:37 ` Joel Brobecker
2013-10-24 13:50 ` Tom Tromey
2013-10-24 15:50 ` Hans-Peter Nilsson [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=201310241547.r9OFlwZ3017071@ignucius.se.axis.com \
--to=hans-peter.nilsson@axis.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
--cc=tromey@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