On Tue, Aug 29, 2017 at 5:58 PM, Neil Bowers wrote:
> Back in February, I asked:
>>> Questions: Are we enough in the future that VMS::stdio can be dropped? And
>>> more relevantly for me, am I ok to drop all the permissions on VMS::stdio?
>>> That would result in VMS::Stdio being indexed for the n
Back in February, I asked:
>> Questions: Are we enough in the future that VMS::stdio can be dropped? And
>> more relevantly for me, am I ok to drop all the permissions on VMS::stdio?
>> That would result in VMS::Stdio being indexed for the next release, though I
>> don’t think the indexing is that
On 02/13/2017 11:22 PM, Neil Bowers wrote:
> Hi,
>
> Exec Summary: am I ok to drop PAUSE permissions
> on PerlIO::Scalar, PerlIO::Via, and VMS::stdio?
>
> I’m writing this wearing my PAUSE admin hat. I’m working through
> clearing up situations where people have permissions on package names
> tha
>> Questions: Are we enough in the future that VMS::stdio can be dropped? And
>> more relevantly for me, am I ok to drop all the permissions on VMS::stdio?
>> That would result in VMS::Stdio being indexed for the next release, though I
>> don’t think the indexing is that much of an issue, since the
On Mon, Feb 13, 2017 at 3:22 PM, Neil Bowers wrote:
> The pair of VMS::stdio and VMS::Stdio is a bit more tricky:
>
> ext/VMS-Stdio/Stdio.pm starts with the expected:
>
> package VMS::Stdio;
>
>
> but then later on we see:
>
>
>
