Yes, unintended. It was only supposed to be signed, but "Send Later"
encrypts it.
Unpacked version:
On 10/2/2018 1:07 AM, Benjamin Peterson wrote:
> On Mon, Oct 1, 2018, at 12:12, Michael Felt wrote:
>> Hi all,
>>
>> Before I submit a patch to increase the default MAXDATA setting for AIX
>> wh
> On 2 Oct 2018, at 12:29, Michael Felt wrote:
>
>
Michael, this message looks encrypted on my end. For people without your public
key, it's impossible to read. This was probably unintentional on your end. In
either case I'd avoid encrypting messages that go to public mailing lists.
- Ł
s
mime-attachment
Description: application/pgp-encrypted
encrypted.asc
Description: Binary data
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/
On Mon, Oct 1, 2018, at 12:12, Michael Felt wrote:
> Hi all,
>
> Before I submit a patch to increase the default MAXDATA setting for AIX
> when in 32-bit mode - I want to know if I can put this LDFLAG setting in
> LDLAST, or if I should introduce a new AC_SUBST() variable (e.g.,
> LDMAXDATA).
Hi all,
Before I submit a patch to increase the default MAXDATA setting for AIX
when in 32-bit mode - I want to know if I can put this LDFLAG setting in
LDLAST, or if I should introduce a new AC_SUBST() variable (e.g.,
LDMAXDATA).
I have not looked yet, but I was thinking that MAYBE! LDLAST is in
