Commit 7874d6ea0c3b984cfc786a6c5995b27e4450314e

Authored by Lars Tiede
1 parent 80f26660

small fix

Showing 1 changed file with 1 additions and 1 deletions   Show diff stats
README.md
... ... @@ -82,7 +82,7 @@ git submodule update --init --recursive
82 82  
83 83 That command clones submodules if they haven't been cloned yet, and it pulls a new commit when parent's reference has changed. So that command is what you also have to do after every 'git pull' of parent. This is the second big headache with submodules: you have to remember to update the submodules after 'git pull'.
84 84  
85   -But that's basically it, now you know how submodules work. Delete your branch now so that there is no pollution here:
  85 +But that's basically it, now you know how submodules work. Delete your branch now so that there is no pollution on source.uit.no:
86 86  
87 87 ```bash
88 88 git push origin --delete YOUR_BRANCH_NAME
... ...