{"thread":{"id":"8909","subject":"[PATCH] Change \"added.moved or removed\" to \"added, moved or removed\" in","startedAt":"2007-07-07T01:23:54Z","lastAt":"2007-07-07T01:23:54Z","messageCount":1,"participants":["Matt Kraai"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"46668","messageId":"118377143481-git-send-email-kraai@ftbfs.org","threadId":"8909","inReplyTo":null,"subject":"[PATCH] Change \"added.moved or removed\" to \"added, moved or removed\" in","fromName":"Matt Kraai","fromEmail":"kraai@ftbfs.org","sentAt":"2007-07-07T01:23:54Z","receivedAt":"2007-07-07T01:23:54Z","isPatch":true,"sender":{"key":"kraai@ftbfs.org","avatar":null},"body":"Signed-off-by: Matt Kraai <kraai@ftbfs.org>\n---\n Documentation/core-intro.txt |    2 +-\n 1 files changed, 1 insertions(+), 1 deletions(-)\n\ndiff --git a/Documentation/core-intro.txt b/Documentation/core-intro.txt\nindex eea44d9..f3cc223 100644\n--- a/Documentation/core-intro.txt\n+++ b/Documentation/core-intro.txt\n@@ -528,7 +528,7 @@ paths that have been trivially merged.\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n \n Sadly, many merges aren't trivial. If there are files that have\n-been added.moved or removed, or if both branches have modified the\n+been added, moved or removed, or if both branches have modified the\n same file, you will be left with an index tree that contains \"merge\n entries\" in it. Such an index tree can 'NOT' be written out to a tree\n object, and you will have to resolve any such merge clashes using\n-- \n1.5.2.3\n"}]}