From 1a805c1f7ce2b4ab36b9470fa0243fd71c907cf0 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 3 May 2016 15:12:55 -0400 Subject: [PATCH] comment --- ...1_eff1bec0af5e7a7364d2fdaea6a8826f._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/todo/drop_--batch/comment_1_eff1bec0af5e7a7364d2fdaea6a8826f._comment diff --git a/doc/todo/drop_--batch/comment_1_eff1bec0af5e7a7364d2fdaea6a8826f._comment b/doc/todo/drop_--batch/comment_1_eff1bec0af5e7a7364d2fdaea6a8826f._comment new file mode 100644 index 0000000000..d921d9ee06 --- /dev/null +++ b/doc/todo/drop_--batch/comment_1_eff1bec0af5e7a7364d2fdaea6a8826f._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-05-03T19:06:53Z" + content=""" +Might be better to make `dropkey` do the same numcopies checking as +`drop` does. Currently, `dropkey` needs `--force` to do anything (and it's +always needed that), so it could do numcopies checking when not forced, +without breaking backwards compatability. + +The benefit of keeping this in `dropkey` is that dropping by key +tends to work better with batch adds/imports of files that are occurring at +the same time. + +Only downside I see is that dropping by key is unable to honor +.gitattributes numcopies settings, since the associated filename is not +known. +"""]]