public inbox for rhug-rhats@sourceware.org
 help / color / mirror / Atom feed
From: Anthony Green <green@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Gary Benson <gbenson@redhat.com>, rhug-rhats@sources.redhat.com
Subject: Re: rhug/commons-beanutils ChangeLog configure con ...
Date: Thu, 30 Jan 2003 21:44:00 -0000	[thread overview]
Message-ID: <1043963252.1704.22.camel@escape> (raw)
In-Reply-To: <877kcmbmpu.fsf@fleche.redhat.com>

On Thu, 2003-01-30 at 08:56, Tom Tromey wrote:
> >>>>> "Gary" == Gary Benson <gbenson@redhat.com> writes:
> 
> Gary> Aha.  By the way, why do the gcc folks recommend doing that?

Also because we like to build multiple toolchains from the same sources
(targeting different processors, for instance).

AG


      reply	other threads:[~2003-01-30 21:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030130021210.6795.qmail@sources.redhat.com>
2003-01-30 10:16 ` Gary Benson
2003-01-30 16:42   ` Tom Tromey
2003-01-30 16:46     ` Gary Benson
2003-01-30 17:04       ` Tom Tromey
2003-01-30 21:44         ` 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=1043963252.1704.22.camel@escape \
    --to=green@redhat.com \
    --cc=gbenson@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).