Bill Ruppert

• Website: www.billruppert.com
• About: Perl programmer since 1996.

Recent Actions

• Commented on Being nice to colleagues with git pre-commit hooks
  I misread the title as meaning "How you can be nice to your colleagues who are afflicted with git pre-commit hooks." lol. +1 with Boris on die and bail....
• Commented on Whats wrong with the Perl Community?
  I follow lots of Perl blogs and I'm surprised you feel the discussion has been negative, or that folks have been saying negative things about Perl. What I've seen are people who are passionate about our favorite programming language struggling...
• Commented on Perl 7 - Final Thoughts
  I liked the Perl 7 idea, but it seems clear that Perl 5 is the end of the line (major number wise) for the Perl we use now. The future of Perl is Perl 6 and its successors, Perl 7,...
• Commented on On the version number succeeding Perl 5
  I love this idea....
• Commented on Perl case studies
  I'd love to see such a series. I assume it would be good for Perl, always nice to have some testimonials. As far as who goes, anyone is fine by me. There are many more small and medium businesses that...

Comment Threads

• Gábor Szabó - גאבור סבו commented on Being nice to colleagues with git pre-commit hooks

  You know, I always wondered why is that behaviour not controllable by environment variables: During development I'd always want bailonfail but that should not go out to production. Not even the repository.

• Ovid commented on Being nice to colleagues with git pre-commit hooks

  Gabor, I'm wondering if I'm misunderstanding you, but that behavior is configurable via environment variables.

• Gábor Szabó - גאבור סבו commented on Being nice to colleagues with git pre-commit hooks

  Ovid, so either I can't read or it was added after I read the docs :) Thanks for pointing those out.

• Buddy Burden commented on Being nice to colleagues with git pre-commit hooks

  I also use the $BAIL_ON_FAIL environment variable instead of the 'bail' module parameter. In fact, I have a script (named t, for brevity) that runs prove with this variable set. That way, when I want to do TDD, I use t, and when I'm ready for full unit testing, I can use make test or whatnot.

• Chad A. Davis commented on Being nice to colleagues with git pre-commit hooks

  And if you work with multiple git repos and want to always be using the same pre-commit safety hook, you can just do something like:

  DIR=~/.git-template/
  mkdir $DIR
  cp .git/hooks/pre-commit $DIR
  # Then in your ~/.bashrc
  export GIT_TEMPLATE_DIR=$DIR
  # Then any subsequent clone ...
  git clone https:/.... 
  # ... now also includes your hook