Toni Uebernickel

My two cents on subtree bundles:

• http://toni.uebernickel.info/2012/02/13/Using-git-subtree-example-symfony2-bundle-on-cloudcontrol.html
• http://toni.uebernickel.info/2012/02/15/Merge-git-subtree-on-failing-path-guessing.html

My two cents on git rebase:

• http://toni.uebernickel.info/2012/02/18/git-rebase-is-not-a-lion-it-is-a-cat-part-one.html
• http://toni.uebernickel.info/2012/02/20/git-rebase-is-not-a-lion-it-is-a-cat-part-two.html

Be aware: git revert is actually creating a new commit containing the reverse version of the patch resulting from the commit to revert. This may result in conflicts depending how far away the commit in question is from your current HEAD and what changed since then! git revert is not aware of changes between that commit and HEAD.

I got this alias, which is based on naming conventions.

https://gist.github.com/2046776

Alternative without sed: find . -type f -name '*.php' -exec php -l {} > /dev/null +

@vladimiroff Your command is doing something completely different.
You are comparing branches on your local repository, not the deployed branch with your local one.

production is a remote, not a branch!