Wiki source code of git
Version 143.1 by Kieran Kelleher on 2011/03/22 01:44
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
135.1 | 1 | = Learning About git = |
| 2 | |||
| 3 | [[Free Online Pro Git book>>http://progit.org/book/]] | ||
| 4 | [[Git User Manual>>http://www.kernel.org/pub/software/scm/git/docs/user-manual.html]] | ||
| 5 | [[Git Reference>>http://gitref.org/index.html]] | ||
| |
137.1 | 6 | [[Linus Torvalds talks about git>>http://www.youtube.com/watch?v=4XpnKHJAok8]] |
| |
135.1 | 7 | |
| 8 | = Install Git = | ||
| 9 | |||
| |
137.1 | 10 | [[OS X dmg Installer>>http://code.google.com/p/git-osx-installer/]] |
| |
135.1 | 11 | |
| 12 | = Git Goodies = | ||
| 13 | |||
| |
137.1 | 14 | === Git Bash Completion === |
| |
135.1 | 15 | |
| |
137.1 | 16 | This is really an absolute necessity and a **huge** productivity improvement. Basically you need the bash completion script from the source tarball and use your shell profile to include it whenever you open a shell. Just google "git bash completion" or check out the tips here to set it up: |
| 17 | [[Git Bash Completion>>http://superuser.com/questions/31744/how-to-get-git-completion-bash-to-work-on-mac-os-x]] | ||
| 18 | |||
| 19 | === GitX git GUI === | ||
| 20 | |||
| 21 | GitX is an awesome FREE history viewer made for OS X. It is a better way to visualize your branch and commit history of your git repository. However, power users (aka "cool kids") will probably only use it for history viewing while they continue to use the terminal command line for checkouts, branching, staging, rebasing and committing. | ||
| |
135.1 | 22 | [[GitX Home Page>>http://gitx.frim.nl/]] |
| 23 | |||
| |
137.1 | 24 | === Open in GitX === |
| |
135.1 | 25 | |
| 26 | [[Open In GitX Finder Droplet>>http://code.google.com/p/git-osx-installer/wiki/OpenInGitX]] | ||
| 27 | |||
| 28 | == Git Tower == | ||
| 29 | |||
| 30 | For those of you who just get panic attacks at the thought of using the Terminal, there is a commercial app for that: | ||
| 31 | [[Git Tower>>http://www.git-tower.com/]] | ||
| 32 | |||
| 33 | = Using git locally on a Subversion Working Copy = | ||
| |
137.1 | 34 | |
| 35 | OK, so you are addicted to git, and now you have to work on a team project that is hosted in a remote subversion repository ... and it is making you depressed :-(. Well, you can use manage your local svn working copy using git and be happy again! | ||
| 36 | |||
| 37 | There is a git-svn tool (type man git-svn in the terminal for details), but that adds yet another tool into the mix that you have to learn. So while you could use it and YMMV for projects tht are going to be on svn forever, I recommend you just use the [[git+svn protocol>>http://www.lostechies.com/blogs/derickbailey/archive/2010/02/03/branch-per-feature-how-i-manage-subversion-with-git-branches.aspx]] instead, especially if you are typically working on one particular branch of the remote svn repository. | ||
| 38 | |||
| 39 | = I want to learn git before I switch from Subversion = | ||
| 40 | |||
| 41 | (This kind of repeats some of the previous section, but that's on purpose so we can condition you brain to start using git right now ;-) ) | ||
| 42 | Even while you are working with svn repositories, you can start learning and taking advantage of git right now by making your local svn working copy an actual local git repository. The idea is to use the appropriate ignore feature of each SCM system to ignore the hidden files of the other system. The concept is described here: | ||
| 43 | |||
| 44 | [[**git+svn** Working Protocol>>http://www.lostechies.com/blogs/derickbailey/archive/2010/02/03/branch-per-feature-how-i-manage-subversion-with-git-branches.aspx]] | ||
| 45 | |||
| 46 | When you first learn about git and you google "git svn" you will learn about a command line tool git-svn which works directly with remote svn repos. Unless you want to use git locally to switch between svn branches, I don't recommend it. Use the **git+svn** approach outlined in above blog post instead. | ||
| 47 | |||
| 48 | Once you start using git, it becomes addictive ....... you can never go back ...... really, it's that good ...... and it is not hard. | ||
| 49 | |||
| 50 | Some tips for Eclipse setup and general workflow when using git locally on svn working copies, | ||
| 51 | |||
| 52 | * check out the entire svn branch that you work on using the command line, then LINK (import no copy) the projects you want in your workspace using the Subclipse import tool, and | ||
| 53 | * Do your git operations (status, staging, commit, diff, branching, checkouts, rebase and merge using the terminal). git on the terminal is efficient... honest. | ||
| 54 | * Do all your local work and cimmits on branches other than the master branch. | ||
| 55 | * Switch to master branch to update from svn and commit those svn updates on the master branch. | ||
| 56 | * Merge your working branch(es) with or rebase your working branch(es) from the master and just keep on working. | ||
| 57 | * Switch to master branch before synchronizing with remote svn repo. | ||
| 58 | * You can use ##git stash## to temporarily put aside your uncommitted changes before doing an svn update. Then use ##git stash pop## to replay those uncommitted changes onto the working copy. | ||
| 59 | |||
| |
143.1 | 60 | {{code title="Mechanics of an svn update operation on a git-managed svn working copy"}} |
| |
137.1 | 61 | |
| 62 | |||
| 63 | # Assume you are currently on a working branch. Verify this and check for uncommitted changes. | ||
| 64 | git status | ||
| 65 | |||
| 66 | # Either commit your local changes to your working branch | ||
| 67 | # using 'git add' + 'git commit', or temporarily stash | ||
| 68 | # them using 'git stash' | ||
| 69 | git stash | ||
| 70 | |||
| 71 | # Switch to master branch | ||
| 72 | git checkout master | ||
| 73 | |||
| 74 | # Ensure there are no changes either from an svn perspective | ||
| 75 | # or a git perspective on the master branch. | ||
| 76 | git status | ||
| 77 | svn status | ||
| 78 | |||
| 79 | # Update the master branch from remote svn repo | ||
| 80 | svn update | ||
| 81 | |||
| 82 | # Commit those updates to git repo | ||
| 83 | git commit -a -m "updated from remote svn repo" | ||
| 84 | |||
| 85 | # Switch to your working branch | ||
| 86 | git checkout workingbranch | ||
| 87 | |||
| 88 | # Merge or rebase your working branch off of the updated master. | ||
| 89 | # This rewinds your branch commits back to the common commit ancestor | ||
| 90 | # shared between your working branch and the master branch. Then it | ||
| 91 | # applies the master branch commits (the svn updates) so that this | ||
| 92 | # working branch becomes identical to the master. After that it 'replays' | ||
| 93 | # your working branch commits on top of the updated branch. | ||
| 94 | # This ensures a clean linear progression. Rebasing is a very cool feature of git. | ||
| 95 | rebase master | ||
| 96 | |||
| 97 | # Now if you stashed uncommitted changes earlier, you can pop them back into | ||
| 98 | # the working copy | ||
| 99 | git stash pop | ||
| 100 | |||
| 101 | {{/code}} | ||
| |
143.1 | 102 | |
| 103 | {{code title="Mechanics of an svn commit operation from a git-managed svn working copy"}} | ||
| 104 | |||
| 105 | # First perform an svn update as outlined above in the previous section | ||
| 106 | |||
| 107 | # Switch to the master branch | ||
| 108 | git checkout master | ||
| 109 | |||
| 110 | # Merge your working branch with the master | ||
| 111 | git merge workingbranch | ||
| 112 | |||
| 113 | # Use svn status, svn add and svn commit to commit your changes to the remote svn repository | ||
| 114 | |||
| 115 | # Switch back to your workingbranch and get back to work. | ||
| 116 | |||
| 117 | |||
| 118 | {{/code}} |