From 44739733a11d320d47c0c2b67b607f872f34352a Mon Sep 17 00:00:00 2001
From: 
 "https://www.google.com/accounts/o8/id?id=AItOawnVnsqEy82M-MuS2gLri-az83wSQ6lXSrc"
 <Jean@web>
Date: Tue, 7 Apr 2015 06:45:49 +0000
Subject: [PATCH]

---
 doc/forum/Why_are_we_stopping_at_a_duplicate__63__.mdwn | 9 +++++++++
 1 file changed, 9 insertions(+)
 create mode 100644 doc/forum/Why_are_we_stopping_at_a_duplicate__63__.mdwn

diff --git a/doc/forum/Why_are_we_stopping_at_a_duplicate__63__.mdwn b/doc/forum/Why_are_we_stopping_at_a_duplicate__63__.mdwn
new file mode 100644
index 0000000000..b14af4be62
--- /dev/null
+++ b/doc/forum/Why_are_we_stopping_at_a_duplicate__63__.mdwn
@@ -0,0 +1,9 @@
+What does the following mean? I would expect that if we encounter a duplicate while using the `--deduplicate` option, the duplicate file would be removed from the import location and import would continue. Does that mean that the newly encountered `img_0405.jpg` is different from the one previously seen? 
+Could the error message perhaps be improved?
+
+```
+.../usbdisk/annex(master)$ git annex import --deduplicate ../Pictures/
+import Pictures/2008/10/12/img_0405.jpg git-annex: not overwriting existing Pictures/2008/10/12/img_0405.jpg (use --force to override)
+```
+
+Many other duplicates are being tidied away.