From d297e9ba781d35f7c1d22153e28bc189f746bd43 Mon Sep 17 00:00:00 2001
From: yarikoptic <yarikoptic@web>
Date: Tue, 2 Aug 2022 21:06:06 +0000
Subject: [PATCH] initial report on wanting --dry-run

---
 doc/todo/add_--dry-run.mdwn | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)
 create mode 100644 doc/todo/add_--dry-run.mdwn

diff --git a/doc/todo/add_--dry-run.mdwn b/doc/todo/add_--dry-run.mdwn
new file mode 100644
index 0000000000..7eab779ccc
--- /dev/null
+++ b/doc/todo/add_--dry-run.mdwn
@@ -0,0 +1,24 @@
+Previous discussion which touched upon it was [7 years ago](https://git-annex.branchable.com/todo/wishlist__58___--dry-run_option_for_all_commands/) (unless I missed some) where part of the response was 
+
+> I don't see the benefit to justify this work. git annex add is entirely predictable; it's very similar to git add. Which itself lacks a dry-run option. 
+
+Oh well:
+
+```
+$> git add --help | grep -e '-n, --dry' -A1
+       -n, --dry-run
+           Don’t actually add the file(s), just show if they exist and/or will be ignored.
+
+```
+and users [submit requests against DataLad](https://github.com/datalad/datalad/issues/6909) to be able to discover what file would go to git and which to git-annex. Also would be useful to know if to git-annex -- would it be locked or unlocked?  Someone else might even want to discover what would be the annex key if it would go into annex, but so far I do not think it is within our desired use-case and it might be too lengthy to compute the key checksum etc.
+
+As for 
+
+> And like git add, you can certianly undo the effects of git annex add.
+
+
+well -- unless there was a version staged already you don't want to loose etc.
+
+[[!meta author=yoh]]
+[[!tag projects/datalad]]
+