Difference between revisions of "Talk:Git"
From GnuCash
(alternative suggestion) |
(→Multiple branches in separate directories?: new section) |
||
| Line 6: | Line 6: | ||
worked for me (I think) | worked for me (I think) | ||
--[[User:Tim abell|Tim abell]] 17:34, 29 May 2008 (EDT) | --[[User:Tim abell|Tim abell]] 17:34, 29 May 2008 (EDT) | ||
| + | |||
| + | == Multiple branches in separate directories? == | ||
| + | |||
| + | [1] recommends that if you work with multiple branches, to have each branch in a separate local Git clone because checking out branches causes Git to change all files and thus forces a full build when you next run make. | ||
| + | |||
| + | Has this been verified? From what I understand, checking out Git topic branches only causes Git to change files which are actually different--files which have the same content across both the branches are left untouched. | ||
| + | |||
| + | [1] http://wiki.gnucash.org/wiki/Git#Multi-Branch_Setup | ||
Revision as of 04:20, 31 October 2010
how about
svn info http://svn.gnucash.org/repo/gnucash/trunk/
to get the latest version number, then with the correct revision number:
git svn clone -r[rev#] http://svn.gnucash.org/repo/gnucash/trunk . git svn rebase
worked for me (I think) --Tim abell 17:34, 29 May 2008 (EDT)
Multiple branches in separate directories?
[1] recommends that if you work with multiple branches, to have each branch in a separate local Git clone because checking out branches causes Git to change all files and thus forces a full build when you next run make.
Has this been verified? From what I understand, checking out Git topic branches only causes Git to change files which are actually different--files which have the same content across both the branches are left untouched.
