From ef037b9028bb9429aad2255e1de39d0f60756a5c Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 24 Aug 2022 13:26:42 -0400 Subject: [PATCH] comment --- ...t_2_5083e5a729f56dab76bdc97fb247b902._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/todo/make_add_--batch_add_directories_content/comment_2_5083e5a729f56dab76bdc97fb247b902._comment diff --git a/doc/todo/make_add_--batch_add_directories_content/comment_2_5083e5a729f56dab76bdc97fb247b902._comment b/doc/todo/make_add_--batch_add_directories_content/comment_2_5083e5a729f56dab76bdc97fb247b902._comment new file mode 100644 index 0000000000..981dd1825e --- /dev/null +++ b/doc/todo/make_add_--batch_add_directories_content/comment_2_5083e5a729f56dab76bdc97fb247b902._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2022-08-24T17:19:02Z" + content=""" +The reason it does not recurse is that would make the number of lines/json +records of output vary depending on the number of files in the directory. +Which would complicate parsing git-annex's output. + +`git-annex add` is not actually special here. You can't +pass a directory to `git-annex drop --batch` either. + +It seems to me that it's not hard to recurse directories yourself, and so +it's better to offload the need to do that onto users of --batch, rather +than making them deal with increased parsing complexity. +"""]]