[Omaha.pm] best practice: podchecker

Jay Hannah jhannah at omnihotels.com
Mon Jun 6 15:58:42 PDT 2005


> 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 at 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.





More information about the Omaha-pm mailing list