ANNOUNCE: cvscheckphp.sh

From: Turadg Aleahmad (turadg_at_users.sourceforge.net)
Date: 12/31/03


Date: 31 Dec 2003 11:01:31 -0800

Hi. I whipped up a little script recently that can be used by CVS to
check all PHP files for syntax before committing. It's not a
technological breakthrough, but it is quite handy. Whenever you run
"cvs commit" it'll run each committed file through PHP's lint check
(php -l) and if any fail the commit will abort.

You can download it off the php-mode page:
http://php-mode.sourceforge.net/

I'd paste it here, but I'm curious to see the SourceForge download
stats.

Enjoy,
Turadg



Relevant Pages

  • Re: CVS history access?
    ... FreeBSD src CVS commit history as a datasource. ... Yo should change `CHANGE_THIS' with the hostname of a CVSup mirror (a ...
    (freebsd-questions)
  • [BK] cvs export
    ... A while back someone complained about the CVS exporter because it ... sometimes groups a pile of BK changesets into one commit. ... If so, I have to agree with you, this is a limitation of the CVS exporter. ...
    (Linux-Kernel)
  • Re: merging other repos into linux-2.6
    ... and start making the history overly complex? ... Quite frankly, if it comes from CVS, I expect the logs, for example, to be ... commit messages (ok, so they're not "commits" in CVS, but you know what I ... automate it sanely will get written. ...
    (Linux-Kernel)
  • Re: CVS history access?
    ... FreeBSD src CVS commit history as a datasource. ... repo-copies and renames of raw repository files have been done without ...
    (freebsd-questions)
  • Re: CVS Newbie
    ... >> I've been using RCS and now I need to move to CVS. ... They are mutual-exclusion-atomic at the tree level. ... The first statement means that if a CVS commit fails midway through, ... matters much more than the failure atomicity, ...
    (alt.os.linux.suse)