From: Ian Lance Taylor <ian@airs.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: overseers@gcc.gnu.org, Ben Elliston <bje@au.ibm.com>
Subject: Re: texinfo 4.8 update
Date: Fri, 11 Feb 2005 21:25:00 -0000 [thread overview]
Message-ID: <m3acqcfq9k.fsf@gossamer.airs.com> (raw)
In-Reply-To: <Pine.BSF.4.62.0502101050130.36652@acrux.dbai.tuwien.ac.at>
Gerald Pfeifer <gerald@pfeifer.com> writes:
> Could we please have texinfo updated to version 4.8 on sourceware?
>
> This contains some changes triggered by reports of mine. I believe
> Ben has already tested this version as well (and reported an issue
> that has been resolved for the final release).
In general we try to keep sourceware on supported RPMs using up2date
whenever possible. That makes it much easier for us to keep the
system up to date with security patches and bug fixes. up2date can't
yet find a texinfo 4.8 RPM.
Is this something we can work around until RHL upgrades to texinfo
4.8?
Ian
next prev parent reply other threads:[~2005-02-10 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 23:27 Gerald Pfeifer
2005-02-11 21:25 ` Ian Lance Taylor [this message]
2005-02-12 0:02 ` Christopher Faylor
2005-02-12 0:21 ` Ian Lance Taylor
2005-02-12 1:54 ` Alexandre Oliva
2005-02-12 18:39 ` Christopher Faylor
2005-02-13 15:04 ` Gerald Pfeifer
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=m3acqcfq9k.fsf@gossamer.airs.com \
--to=ian@airs.com \
--cc=bje@au.ibm.com \
--cc=gerald@pfeifer.com \
--cc=overseers@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).