[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Omaha.pm] best practice: podchecker

To: <omaha-pm@pm.org>
Subject: [Omaha.pm] best practice: podchecker
From: "Jay Hannah" <jhannah@omnihotels.com>
Date: Mon, 6 Jun 2005 17:58:42 -0500
Delivered-to: mailman-omaha-pm@mailman.pm.dev
Delivered-to: omaha-pm@pm.org
List-archive: <http://mail.pm.org/pipermail/omaha-pm>
List-help: <mailto:omaha-pm-request@pm.org?subject=help>
List-id: "Perl Mongers of Omaha, Nebraska USA" <omaha-pm.pm.org>
List-post: <mailto:omaha-pm@pm.org>
List-subscribe: <http://mail.pm.org/mailman/listinfo/omaha-pm>, <mailto:omaha-pm-request@pm.org?subject=subscribe>
List-unsubscribe: <http://mail.pm.org/mailman/listinfo/omaha-pm>, <mailto:omaha-pm-request@pm.org?subject=unsubscribe>
Reply-to: "Perl Mongers of Omaha, Nebraska USA" <omaha-pm@pm.org>
Thread-index: AcVmC0up0fz86cbcQ/+is2b6C92CEgE38a7wAAAJfaA=

> See CVS for details.  Unless a server is accessing the sysmaster
> database, updates are not needed at this time.
> DT

Before committing POD changes, always run podchecker please. Please correct so podchecker is happy.

Thanks,

j

jhannah@razorbill:~/Omni> podchecker DB.pm
*** ERROR: Spurious text after =cut at line 237 in file DB.pm
*** ERROR: Spurious text after =cut at line 249 in file DB.pm
DB.pm has 2 pod syntax errors.

Follow-Ups:
- Re: [Omaha.pm] best practice: podchecker
  - From: Andy Lester <andy@petdance.com>

Prev by Date: Re: [Omaha.pm] precedence: ?: vs. =
Next by Date: Re: [Omaha.pm] best practice: podchecker
Previous by thread: Re: [Omaha.pm] precedence: ?: vs. =
Next by thread: Re: [Omaha.pm] best practice: podchecker
Index(es):
- Date
- Thread