AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Github gitify5/1/2023 If we switch the svn branch, git initially doesn't catch the change and the branches differ: > svn switch Īfter re-running gitify init they are the same again: > git branch To remedy this you can either manually switch git or just re-run gitify init: > svn info due to a change in svn:externals or in a buildout source) the branch git is on differs from the current svn branch. If the svn repository switches to another branch (i.e. Notice how the git repository contains both trunk and the 1.1 branch: > git branch This can be further evidenced by looking at the available local branches now. Notice, that this operation went much faster, as we now have used the existing git repository in the cache directory, thus avoiding the slow and network intensive clone operation. Git branch 'local/trunk' is now following svn branch 'trunk': What happens if we run gitify here?: > cd /įetching /Users/tomster/.gitcache/ Let's move our previous checkout out of the way and create a maintenance checkout that follows trunk: > cd. gitcache directory created above comes in handy. In practice you will often work with different local copies of a given repository, i.e. Was called from (in this case ) as it refuses to guess
0 Comments
Read More
Leave a Reply. |