diff options
| author |  Richard Hartmann <richih@debian.org> | 2014-03-05 23:33:28 +0100 |
|---|---|---|
| committer | Richard Hartmann <richih@debian.org> | 2014-03-05 23:33:28 +0100 |
| commit | 71645043a1725b245a4058ee743b9795aca73715 (patch) | |
| tree | 81d9b6d5370a01f7cf2932bbbfbd447f10c616b9 | |
| parent | efe649a97cb4c5cf6a3d9731cebd3049dae114e0 (diff) | |
Typo
| -rw-r--r-- | doc/devblog/day__126-127__merge_fixes.mdwn | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/devblog/day__126-127__merge_fixes.mdwn b/doc/devblog/day__126-127__merge_fixes.mdwn index f46f4b555..f4a57a09d 100644 --- a/doc/devblog/day__126-127__merge_fixes.mdwn +++ b/doc/devblog/day__126-127__merge_fixes.mdwn @@ -8,7 +8,7 @@ Understanding the bug was easy. Fixing it turned out to be hard, because the automatic merge conflict resolution code was quite a mess. In particular, it wrote files to the work tree, which made it difficult for a later stage to detect and handle the abovementioned case. Also, the -automatic merge resolution code had weird asymetric structure that I never +automatic merge resolution code had weird asymmetric structure that I never fully understood, and generally needed to be stared at for an hour to begin to understand it. @@ -27,7 +27,7 @@ Finally this evening, I added support for automatically handling merge conflicts where one side is an annexed file, and the other side has the same filename committed to git in the normal way. This is not an important case, but it's worth it for completeness. There was an unexpected benefit -to doing it; it turned out that the weird asymetric part of the code went +to doing it; it turned out that the weird asymmetric part of the code went away. The final core of the automatic merge conflict resolver has morphed from |