Skip to content

Commit 0eb96c7

Browse files
committed
Merge pull request #460 from brettcannon/patch-1
Fix a grammatical mistake in submodules.asc
2 parents 63e4c62 + 53004a3 commit 0eb96c7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

book/07-git-tools/sections/submodules.asc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -374,7 +374,7 @@ So now let's go through an example of making changes to the submodule at the sam
374374

375375
So far, when we've run the `git submodule update` command to fetch changes from the submodule repositories, Git would get the changes and update the files in the subdirectory but will leave the sub-repository in what's called a ``detached HEAD'' state.
376376
This means that there is no local working branch (like ``master'', for example) tracking changes.
377-
So any changes you make aren't being tracked well.
377+
With no working branch tracking changes, that means even if you commit changes to the submodule, those changes will quite possibly be lost the next time you run `git submodule update`. You have to do some extra steps if you want changes in a submodule to be tracked.
378378

379379
In order to set up your submodule to be easier to go in and hack on, you need do two things.
380380
You need to go into each submodule and check out a branch to work on.

0 commit comments

Comments
 (0)