From: Mike Gilbert <floppym@gentoo.org>
To: djc@gentoo.org
Cc: gentoo-python@lists.gentoo.org
Subject: Re: [gentoo-python] Testing dev-lang/python version bumps
Date: Sat, 28 Apr 2012 13:53:36 -0400 [thread overview]
Message-ID: <4F9C2EA0.8000709@gentoo.org> (raw)
In-Reply-To: <CAKmKYaAzqhH+Y=--RGT7zrHAxM2+1Q6jOtPP0P4b3mhtZiHCnA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
On 04/27/2012 12:35 PM, Dirkjan Ochtman wrote:
> On Fri, Apr 27, 2012 at 17:13, Mike Gilbert <floppym@gentoo.org> wrote:
>> Would you like me to cut a new set of tarballs without 08, 22, and 23?
>
> That would be perfect. I'd also still like to drop 61 unless we have a
> clear picture of what/why it helps (and can document that in the
> patch).
>
I have uploaded new tarballs to my devspace.
http://dev.gentoo.org/~floppym/python/python-gentoo-patches-2.7.3-1.tar.bz2
http://dev.gentoo.org/~floppym/python/python-gentoo-patches-3.2.3-1.tar.bz2
I removed only 08, 22, and 23.
Per my previous message, 61 has legitimate reasons for existing. I do
not believe there is a less intrusive way to accomplish what it is
doing, and removing it would cause the behavior of wrapped python
scripts to change. Do you still want to drop it?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 230 bytes --]
next prev parent reply other threads:[~2012-04-28 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-22 1:12 [gentoo-python] Testing dev-lang/python version bumps Mike Gilbert
2012-04-27 13:03 ` Dirkjan Ochtman
2012-04-27 15:13 ` Mike Gilbert
2012-04-27 16:35 ` Dirkjan Ochtman
2012-04-27 17:17 ` Mike Gilbert
2012-04-27 17:24 ` Mike Gilbert
2012-04-28 17:14 ` Mike Gilbert
2012-04-28 17:53 ` Mike Gilbert [this message]
2012-04-30 6:40 ` Dirkjan Ochtman
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=4F9C2EA0.8000709@gentoo.org \
--to=floppym@gentoo.org \
--cc=djc@gentoo.org \
--cc=gentoo-python@lists.gentoo.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