Git

If you've already been committing code to master, do this to start a new 7.x branch and kill off the code in the master branch so noone gets confused.

A colleague insists that messages abide by the 72 character limit advisory, and i want to change my habit to get the files-changed and, just as important, files-left-out information that git commit will give in the Vim editor.

I'm still a bit addicted to the git commit -m "Message here" workflow of entering messages right in the command line, and it's more than just habit: it is very useful to be able to look at the git add -p record.

Update: Just set it up to be automatic.

For all new projects:

git config --global branch.autosetuprebase always

For existing projects:

git config branch.master.rebase true

Courtesy Randy Fay's blog post, "Simpler Rebasing (avoiding unintentional merge commits)"

git pull --rebase
rebasing applies your changes on top of the fetched commits.

Just created a new sandbox project, and try to push it to d.o:
git push origin master

error: src refspec master does not match any.

When you are putting a new project on Drupal.org means you haven't committed anything yet!

git init is not enough, heh.

(Yes, i googled this before figuring thisout, so if that's how you got here, you are not alone)

Git provides a series of enhancements for the bash prompt. It can display the current branch when inside a working copy. Here's an example from my machine:
{syntaxhighlighter brush: bash; gutter: false}
stefan@debian:~/Documents/Projects/Drupal/test(master *)$
{/syntaxhighlighter}
It shows the branch name and indicates by an asterisk that I have uncommitted changes.

This is for Ubuntu 10.10 with the intention of doing primarily Drupal 7 development.

Get the link to the current version of Drubuntu from the Drubuntu project page, and use it thusly:

wget http://ftp.drupal.org/files/projects/drubuntu-7.x-10.10-beta1.tar.gz
tar -xzf drubuntu-7.x-10.10-beta1.tar.gz

In figuring out what changed in a theme's files (an incorrectly made subtheme; instead of overriding the base themes stylesheets, changes should have gone into its own files with different names), these commands were useful.

diff -uP themes/bartik/css/colors.css sites/default/themes/dgd7theme/css/style.css > theme.diff
git log --cc sites/default/themes/dgd7theme/css/style.css > log.diff

Kept running them for the three different files, and reloading theme.diff and log.diff in gvim to see the changes. Quite convenient.

To revert an entire commit.

git checkout <file>
re-checkout <file>, overwriting any local changes

Should be able to git add changed files that you are interested in committing the revised changes and git commit --amend

http://stackoverflow.com/questions/927358/git-undo-last-commit