diff options
author | 2015-03-30 15:41:13 +0000 | |
---|---|---|
committer | 2015-03-30 15:41:13 +0000 | |
commit | eee064c6af631c04fc587ddcab2c9f97bbb3c1fb (patch) | |
tree | bf7f41a41a9247aa8dacb7afae9e171a02e9a324 | |
parent | c33239b0a3c23f8e86ab5f5f1097ea660bb62f02 (diff) |
-rw-r--r-- | doc/todo/Output_key_with_import__47__deduplicate.mdwn | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/todo/Output_key_with_import__47__deduplicate.mdwn b/doc/todo/Output_key_with_import__47__deduplicate.mdwn new file mode 100644 index 000000000..807d59dfd --- /dev/null +++ b/doc/todo/Output_key_with_import__47__deduplicate.mdwn @@ -0,0 +1,20 @@ +When using + + git annex import --deduplicate -- ~/directory/to/import + +would it be possible to output the keys for duplicate files? This would allow people to find where in the annex the files already exist. + +e.g. + + import ~/directory/to/import/001.txt ok + import ~/directory/to/import/002.txt ok + import ~/directory/to/import/002_d.txt (duplicate SHA256E-s261--fb1230987ac123098...) ok + import ~/directory/to/import/003.txt ok + +Then you could use + + git log -S SHA256E-s261--fb1230987ac123098... + +to find out where it is already. + +Not sure if that is the nicest layout.. (or what it might break). |