From: Anthony Green <green@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: rhug-rhats@sources.redhat.com
Subject: Re: auto* versions
Date: Thu, 30 Jan 2003 06:01:00 -0000 [thread overview]
Message-ID: <1043906665.1490.12.camel@escape> (raw)
In-Reply-To: <87of5zcrg5.fsf@fleche.redhat.com>
On Wed, 2003-01-29 at 18:16, Tom Tromey wrote:
> I noticed the top-level rhug Makefile.in was built using automake 1.5.
> That is an obsolete version, and an unfortunately buggy one at that.
> Let's standardize on something newer, like 1.7.2. What do you think?
I suppose we could try. To be honest, I'm afraid to touch any of this
because it seems so fragile (we're using a hacked libtool, for
instance). I may have some time in the next week to try this.
My plan was to not touch any of this until your new build tool was
ready. half-:-)
AG
prev parent reply other threads:[~2003-01-30 6:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 2:24 Tom Tromey
2003-01-30 6:01 ` Anthony Green [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=1043906665.1490.12.camel@escape \
--to=green@redhat.com \
--cc=rhug-rhats@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).