From 1b8d5940bd4dfc0257d12bad148f941f12a95fa4 Mon Sep 17 00:00:00 2001 From: jkniiv Date: Wed, 12 Jul 2023 07:33:16 +0000 Subject: [PATCH] Added a comment --- ..._3_c03b45321728155eae9470cd8bb2cc93._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/bugs/Changing_sync_to_include_content_breaks_UX/comment_3_c03b45321728155eae9470cd8bb2cc93._comment diff --git a/doc/bugs/Changing_sync_to_include_content_breaks_UX/comment_3_c03b45321728155eae9470cd8bb2cc93._comment b/doc/bugs/Changing_sync_to_include_content_breaks_UX/comment_3_c03b45321728155eae9470cd8bb2cc93._comment new file mode 100644 index 0000000000..11fcf6f9cb --- /dev/null +++ b/doc/bugs/Changing_sync_to_include_content_breaks_UX/comment_3_c03b45321728155eae9470cd8bb2cc93._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="jkniiv" + avatar="http://cdn.libravatar.org/avatar/05fd8b33af7183342153e8013aa3713d" + subject="comment 3" + date="2023-07-12T07:33:16Z" + content=""" +> IIUC, Joeys reasoning is that git annex sync was incomplete/inconsistent from the start and did too many configurable things. + +That's not a reason to break backwards compatibility for such a prominent command as `sync`. Just no. + +> git annex assist syncs the entire repo state - as the assistant. + +I don't want to use the assistant -- or it's CLI alter ego assist -- I want my own manicured commit messages, puh-lease! The assistant +is a whole another use case, just not mine at the moment. + +Just give us our old `sync` back. Rename it to `synk` (or, `sc`/`sk` -- as in \"sync for [k]urmudgeons\") if you want but let us have it. :) +"""]]