From d27b8f0b89a261979e7c102f7f90d3ac838a917b Mon Sep 17 00:00:00 2001 From: Chris Date: Sat, 20 Oct 2018 08:09:41 +0000 Subject: [PATCH] Added a comment --- .../comment_2_8ac7ae6937d219854bc60b56b8646d8b._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/wishlist__58___--dry-run_option_for_all_commands/comment_2_8ac7ae6937d219854bc60b56b8646d8b._comment diff --git a/doc/todo/wishlist__58___--dry-run_option_for_all_commands/comment_2_8ac7ae6937d219854bc60b56b8646d8b._comment b/doc/todo/wishlist__58___--dry-run_option_for_all_commands/comment_2_8ac7ae6937d219854bc60b56b8646d8b._comment new file mode 100644 index 0000000000..d484d5559f --- /dev/null +++ b/doc/todo/wishlist__58___--dry-run_option_for_all_commands/comment_2_8ac7ae6937d219854bc60b56b8646d8b._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Chris" + avatar="http://cdn.libravatar.org/avatar/02b67b7ebace8cb6433504ba9a17d4a4" + subject="comment 2" + date="2018-10-20T08:09:40Z" + content=""" +Hm, IMHO such a “dry-run” flag would be most beneficial for better understanding the preferred/required content settings and try their effect while working on finding the right expression. Therefore, the “drop”, “get” and “sync --content” commands would benefit from such a flag, especially in combination with flags such as “--auto”. Maybe it's just me, but I am not able to utilize the “find” command in a way that it respects preferred content and numcopies and further settings in the same way as the three commands above would do, and testing preferred content expressions is therefore a blind flight. +"""]]