On Sun, Mar 21, 2021 at 1:37 PM Oswald Buddenhagen <oswald.buddenha...@gmx.de> wrote: > didn't you just spend more time on writing that mail than fixing at > least a dozen systems?
Agreed that find-and-replacing those two words in a file isn't that big of a deal, say it takes about 2-3 minutes (including documentation and testing). However, when you factor in all the `mbsync` users, I think we've wasted quite some time... As with the original poster, I don't want to enter this words debate. However it would have been nice to: * just allow the old words to be used and don't issue any warnings; (initially I thought something was broken during the OS upgrade;) * perhaps provide a global option (in the configuration file) that just quiets this warning; * have the man page mention the renaming so that those that see old `mbsync` tutorials and check the man page aren't confused; So, yes I also did spend some time writing this email, perhaps more than 5 times it took to correct the issue. > if you're in the extraordinary situation of > actually having to fix several dozen systems (i'm curious what you're > doing then, btw), you can mostly automate it by running How about the use-case where `mbsync` is called by another tool, which generates the configuration file each time `mbsync` is run? Now the user has to track down the other tool code and correct that... (Hopefully it's not in C/C++ and requires 30 `lib*-dev` dependencies to rebuild...) Otherwise, thanks for the good work for `mbsync`! Ciprian. _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
