| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
http://progit.org/book/ - git book (online and available in print) | ||||||||
| Line: 6 to 6 | ||||||||
| http://jointheconversation.org/2008/06/02/railsconf-git-talk/ - excellent introductory screencast. about an hour long, but well worth it http://macournoyer.wordpress.com/2007/12/27/moron-no-more-i-can-git/ - a nice intro to using git-svn. http://www.sanityinc.com/articles/partial-emacs-git-svn-mode - some tips for emacs and git-svn | ||||||||
| Changed: | ||||||||
| < < | http://www.newartisans.com/blog_files/git.from.bottom.up.php - git from the bottom up http://www.eqqon.com/index.php/Collaborative_Github_Workflow | |||||||
| > > | http://newartisans.com/2008/04/git-from-the-bottom-up/ - git from the bottom up | |||||||
| If you're trying to use a non-default ssh key with git (e.g. for github) then this will help: http://help.github.com/multiple-keys/ | ||||||||
| Line: 62 to 61 | ||||||||
| I usually don't like to have programs like this output anything, but in this case I emit one line because the proxy should run sometimes but not others so it's handy to see whether git has decided to run it or not. The only downside of this is that you need to use fully-qualified domain names for machines in your corporate domain, because git uses the domain name to decide whether to use the proxy or not. \ No newline at end of file | ||||||||
| Added: | ||||||||
| > > |
crongit, ssh, and cron can be a fussy combination. When debugging crontab's that involve git and ssh, it's often helpful to wedge a small script between git and ssh:#!/bin/bash /usr/bin/ssh -vvv "$@"Tell git to use this script with the GIT_SSH environment variable. | |||||||