diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/todo/wishlist:_--dry-run_option_for_all_commands/comment_1_03bf493d5a7f957339f9aa388ba85ef8._comment (renamed from doc/todo/wishlist:__--dry*/comment_1_03bf493d5a7f957339f9aa388ba85ef8._comment) | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/todo/wishlist:__--dry*/comment_1_03bf493d5a7f957339f9aa388ba85ef8._comment b/doc/todo/wishlist:_--dry-run_option_for_all_commands/comment_1_03bf493d5a7f957339f9aa388ba85ef8._comment index 2e314afbc..772574738 100644 --- a/doc/todo/wishlist:__--dry*/comment_1_03bf493d5a7f957339f9aa388ba85ef8._comment +++ b/doc/todo/wishlist:_--dry-run_option_for_all_commands/comment_1_03bf493d5a7f957339f9aa388ba85ef8._comment @@ -12,4 +12,9 @@ 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. And like `git add`, you can certianly undo the effects of `git annex add`. + +Matching options can make commands like `git annex find` list the same +set of files that are acted on by commands like `git annex drop` +(`git annex find --in here`) +and `git annex get` (`git annex find --not --in here`). """]] |