Skip to Content

Changes for page Getting Started with Git

Last modified by Bastian Triller on 2013/05/21 17:24
From version 112.1
edited by Kieran Kelleher
on 2011/03/21 15:06
Change comment: There is no comment for this version
To version 114.1
edited by Kieran Kelleher
on 2011/03/21 15:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -28,17 +28,4 @@
28 28  
29 29  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!
30 30  
31 -Don't use the git-svn tool, 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.
32 -
33 -= I want to learn git before I switch from Subversion =
34 -
35 -(This kind of repeats some of the previous section, but that's on porpose so we can condition you brain to start using git right now ;-) )
36 -Even while you are working with svn repositories, you can start taking learning and 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:
37 -
38 -[[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]]
39 -
40 -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, however my advice is don't use git-svn. Use the approach outlined in above blog post instead.
41 -
42 -Once you start using git, it becomes addictive ....... you can never go back ...... really, it's that good ...... and it is not hard.
43 -
44 -For Eclipse setup when using git locally on svn working copies, just check out the entire svn branch on the command line, then LINK (import no copy) the projects you want in your workspace using the Subclipse import tool, and just do your git operations (status, staging, commit, diff, branching, checkouts, rebase and merge using the terminal). git on the terminal is efficient... honest.
31 +Don't use the git-svn tool, 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