Bug#319615: marked as done (Why not for (EXPR; EXPR; EXPR) BLOCK continue BLOCK ?)

Fri Apr 22 19:15:06 UTC 2016

Your message dated Fri, 22 Apr 2016 22:12:13 +0300
with message-id <20160422191213.GA6787 at estella.local.invalid>
and subject line Re: Bug#319615: Why not for (EXPR; EXPR; EXPR) BLOCK continue BLOCK ?
has caused the Debian Bug report #319615,
regarding Why not for (EXPR; EXPR; EXPR) BLOCK continue BLOCK ?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)

-- 
319615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=319615
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Anthony DeRobertis <asd at suespammers.org>
Subject: Why not for (EXPR; EXPR; EXPR) BLOCK continue BLOCK ?
Date: Sat, 23 Jul 2005 10:25:20 -0400
Size: 2739
URL: <http://lists.alioth.debian.org/pipermail/perl-maintainers/attachments/20160422/c0b4d68d/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Niko Tyni <ntyni at debian.org>
Subject: Re: Bug#319615: Why not for (EXPR; EXPR; EXPR) BLOCK continue BLOCK ?
Date: Fri, 22 Apr 2016 22:12:13 +0300
Size: 3193
URL: <http://lists.alioth.debian.org/pipermail/perl-maintainers/attachments/20160422/c0b4d68d/attachment-0001.mht>