phly, boy, phly (Entries tagged as git)

State of Zend Framework 2.0

nospam@example.com (Matthew Weier O'Phinney) — Fri, 04 Jun 2010 10:00:00 -0400

The past few months have kept myself and my team quite busy, as we've turned our attentions from maintenance of the Zend Framework 1.X series to Zend Framework 2.0. I've been fielding questions regularly about ZF2 lately, and felt it was time to talk about the roadmap for ZF2, what we've done so far, and how the community can help.

Continue reading "State of Zend Framework 2.0"

GPG-signing Git Commits

nospam@example.com (Matthew Weier O'Phinney) — Wed, 24 Mar 2010 12:26:43 -0400

We're working on migrating Zend Framework to Git. One issue we're trying to deal with is enforcing that commits come from CLA signees.

One possibility presented to us was the possibility of utilizing GPG signing of commit messages. Unfortunately, I was able to find little to no information on the 'net about how this might be done, so I started to experiment with some solutions.

The approach I chose utilizes git hooks, specifically the commit-msg hook client-side, and the pre-receive hook server-side.

Continue reading "GPG-signing Git Commits"

Cloning the ZF SVN repository in Git

nospam@example.com (Matthew Weier O'Phinney) — Mon, 31 Aug 2009 12:54:37 -0400

I've been using Git for around a year now. My interest in it originally was to act as a replacement for SVK, with which I'd had some bad experiences (when things go wrong with svk, they go very wrong). Why was I using a distributed version control system, though?

Continue reading "Cloning the ZF SVN repository in Git"

git-svn Tip: don't use core.autocrlf

nospam@example.com (Matthew Weier O'Phinney) — Wed, 24 Sep 2008 12:16:27 -0400

I've been playing around with Git in the past couple months, and have been really enjoying it. Paired with subversion, I get the best of all worlds -- distributed source control when I want it (working on new features or trying out performance tuning), and non-distributed source control for my public commits.

Github suggests that when working with remote repositories, you turn on the autocrlf option, which ensures that changes in line endings do not get accounted for when pushing to and pulling from the remote repo. However, when working with git-svn, this actually causes issues. After turning this option on, I started getting the error "Delta source ended unexpectedly" from git-svn. After a bunch of aimless tinkering, I finally asked myself the questions, "When did this start happening?" and, "Have I changed anything with Git lately?" Once I'd backed out the config change, all started working again.

In summary: don't use "git config --global core.autocrlf true" when using git-svn.