public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: hjl@lucon.org (H.J. Lu)
Cc: egcs@cygnus.com
Subject: Re: texinfo-3.11 merge
Date: Mon, 23 Mar 1998 20:58:00 -0000	[thread overview]
Message-ID: <275.890715576@hurl.cygnus.com> (raw)
In-Reply-To: <m0yHKJo-00058JC@ocean.lucon.org>

  In message < m0yHKJo-00058JC@ocean.lucon.org >you write:
  > > 
  > > 
  > > Just an FYI, I imported texinfo-3.11 into the egcs source tree
  > > to replace whatever old version we were still running.
  > > 
  > 
  > I saw many data files like *.po/*.gmo. Does egcs really need them?
They appear to be part of some multi-language support.

I'd prefer to keep them -- I'd like to see out texinfo tree move as
close to the net distributions as possible.

jeff

  reply	other threads:[~1998-03-23 20:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-23 16:39 Jeffrey A Law
1998-03-23 19:24 ` H.J. Lu
1998-03-23 20:58   ` Jeffrey A Law [this message]
1998-03-24  8:18     ` Lee Iverson
1998-03-24 17:35       ` Jeffrey A Law
1998-03-24  0:03   ` Akim Demaille
1998-03-24 11:16 ` texinfo-3.11 merge (or 3.12 ?) Philippe De Muyter

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=275.890715576@hurl.cygnus.com \
    --to=law@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=hjl@lucon.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).