From: Andrew Haley <aph@redhat.com>
To: java@gcc.gnu.org
Subject: Re: Another Python namespace pollution
Date: Fri, 18 Feb 2011 14:32:00 -0000 [thread overview]
Message-ID: <4D5E82EF.5030801@redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1102181520080.7945@gerinyyl.fvgr>
On 02/18/2011 02:20 PM, Gerald Pfeifer wrote:
> On Wed, 2 Feb 2011, Gary Benson wrote:
>> Ok, attached is a patch that causes the two Python modules to be
>> installed in a versioned directory.
>
> Thanks, Gary! I see you committed this to HEAD; any chance you could
> also push this to the GCC 4.5 branch which is our latest release(d)
> branch?
4.5 is in serious regression fixes only mode. What do you need this
for?
Andrew.
prev parent reply other threads:[~2011-02-18 14:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090528171422.508.qmail@sourceware.org>
[not found] ` <Pine.LNX.4.64.0905282258430.24872@digraph.polyomino.org.uk>
[not found] ` <m33aan21h4.fsf@fleche.redhat.com>
[not found] ` <Pine.LNX.4.64.0905291955130.18075@digraph.polyomino.org.uk>
[not found] ` <m3y6sfzk3y.fsf@fleche.redhat.com>
[not found] ` <m3ljofzhtd.fsf@fleche.redhat.com>
2011-01-27 1:48 ` Another Python namespace pollution (was: r147958 - in /trunk/libstdc++-v3: ChangeLog Mak...) Gerald Pfeifer
2011-01-27 10:38 ` Gary Benson
2011-01-27 10:43 ` Richard Guenther
2011-01-27 11:00 ` Gary Benson
2011-01-27 19:54 ` Gerald Pfeifer
2011-01-27 23:59 ` Another Python namespace pollution Matthias Klose
2011-02-02 15:00 ` Another Python namespace pollution (was: r147958 - in /trunk/libstdc++-v3: ChangeLog Mak...) Gary Benson
2011-02-18 14:21 ` Gerald Pfeifer
2011-02-18 14:32 ` Andrew Haley [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=4D5E82EF.5030801@redhat.com \
--to=aph@redhat.com \
--cc=java@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).