From 9d305081c460c32aff74c54f4471453835c0ee7a Mon Sep 17 00:00:00 2001 From: nobodyinperson Date: Wed, 5 Jul 2023 20:46:13 +0000 Subject: [PATCH] Added a comment --- ...comment_1_81644886e14851a276dc3c89965df62e._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/todo/option_to_explain/comment_1_81644886e14851a276dc3c89965df62e._comment diff --git a/doc/todo/option_to_explain/comment_1_81644886e14851a276dc3c89965df62e._comment b/doc/todo/option_to_explain/comment_1_81644886e14851a276dc3c89965df62e._comment new file mode 100644 index 0000000000..b702a50c81 --- /dev/null +++ b/doc/todo/option_to_explain/comment_1_81644886e14851a276dc3c89965df62e._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="nobodyinperson" + avatar="http://cdn.libravatar.org/avatar/736a41cd4988ede057bae805d000f4f5" + subject="comment 1" + date="2023-07-05T20:46:13Z" + content=""" +Sounds absolutely awesome! The new `git annex satisfy` would also benefit from this. + +Also when thinking about a potential future `--dry-run` mode that wouldn't actually do stuff but in combination with `--explain` would display what it would do and why. I know dry-running can be nontrivial to implement, especially when actions change state. But imagine how cool it would be to do `git annex assist --dry-run --explain` and to see what exactly it *would* do (what files go to git, which to the annex, what files will be copied where, etc.) 🤩 +"""]]