Skip Menu |

This queue is for tickets about the Getopt-Long CPAN distribution.

Report information
The Basics
Id: 26742
Status: resolved
Priority: 0/
Queue: Getopt-Long

People
Owner: jv [...] cpan.org
Requestors: gaashh [...] yahoo.com
Cc:
AdminCc:

Bug Information
Severity: Unimportant
Broken in: 2.36
Fixed in: 2.37



Subject: Minor documentation typo
Getopt-Long minor documentation typo. Configuring Getopt::Long/permute, following the "--foo arg1 --bar arg2 -- arg3" example it says ".... and then terminate GetOptions() leaving "arg2" in @ARGV." I belive it should say " ... leaving *arg3* in @ARGV"
From: JV [...] cpan.org
Thanks, fixed.
Subject: Re: [rt.cpan.org #26742] Minor documentation typo
Date: Fri, 27 Apr 2007 06:03:36 -0700 (PDT)
To: bug-Getopt-Long [...] rt.cpan.org
From: Gaash Hazan <gaashh [...] yahoo.com>
It was quick, thank you! Gaash Johan_Vromans via RT <bug-Getopt-Long@rt.cpan.org> wrote: Thanks, fixed.
Subject: Re: [rt.cpan.org #26742] Resolved: Minor documentation typo
Date: Tue, 1 Jan 2008 09:33:06 -0800 (PST)
To: bug-Getopt-Long [...] rt.cpan.org
From: Gaash Hazan <gaashh [...] yahoo.com>
thank you! --- Johan Vromans via RT <bug-Getopt-Long@rt.cpan.org> wrote: Show quoted text
> <URL: > http://rt.cpan.org/Ticket/Display.html?id=26742 > > > According to our records, your request has been > resolved. If you have any > further questions or concerns, please respond to > this message. >
Subject: Re: [rt.cpan.org #26742] Resolved: Minor documentation typo
Date: Sun, 7 Sep 2008 11:50:27 -0700 (PDT)
To: bug-Getopt-Long [...] rt.cpan.org
From: Gaash Hazan <gaashh [...] yahoo.com>
Thank you! --- On Sun, 9/7/08, Johan Vromans via RT <bug-Getopt-Long@rt.cpan.org> wrote: Show quoted text
> From: Johan Vromans via RT <bug-Getopt-Long@rt.cpan.org> > Subject: [rt.cpan.org #26742] Resolved: Minor documentation typo > To: gaashh@yahoo.com > Date: Sunday, September 7, 2008, 9:49 PM > <URL: http://rt.cpan.org/Ticket/Display.html?id=26742
> >
> > According to our records, your request has been resolved. > If you have any > further questions or concerns, please respond to this > message.