File tree Expand file tree Collapse file tree 1 file changed +6
-3
lines changed
book/07-git-tools/sections Expand file tree Collapse file tree 1 file changed +6
-3
lines changed Original file line number Diff line number Diff line change 3838
3939In one branch we change the word "`hello`" to "`hola`", then in another branch we change the "`world`" to "`mundo`", just like before.
4040
41- image::images/rerere1.png[]
41+ .Two branches changing the same part of the same file differently
42+ image::images/rerere1.png[Two branches changing the same part of the same file differently]
4243
4344When we merge the two branches together, we'll get a merge conflict:
4445
@@ -143,7 +144,8 @@ Recorded resolution for 'hello.rb'.
143144
144145You can see that it "Recorded resolution for FILE".
145146
146- image::images/rerere2.png[]
147+ .Recorded resolution for FILE
148+ image::images/rerere2.png[Recorded resolution for FILE]
147149
148150Now, let's undo that merge and then rebase it on top of our `master` branch instead.
149151We can move our branch back by using `git reset` as we saw in <<ch07-git-tools#_git_reset>>.
@@ -205,7 +207,8 @@ index a440db6,54336ba..0000000
205207 end
206208----
207209
208- image::images/rerere3.png[]
210+ .Automatically resolved merge conflict using previous resolution
211+ image::images/rerere3.png[Automatically resolved merge conflict using previous resolution]
209212
210213You can also recreate the conflicted file state with `git checkout`:
211214
You can’t perform that action at this time.
0 commit comments