deprecate the compat wrapper

after a decade, it's about time to phase it out.
This commit is contained in:
Oswald Buddenhagen 2014-07-12 13:50:12 +02:00
parent 2a3963af58
commit 3742fc475b
3 changed files with 10 additions and 0 deletions

4
NEWS
View File

@ -1,3 +1,7 @@
[1.2.0]
The 'isync' compatibility wrapper is now deprecated.
[1.1.0] [1.1.0]
Support for hierarchical mailboxes in Patterns. Support for hierarchical mailboxes in Patterns.

View File

@ -37,6 +37,9 @@ It will automatically migrate the UID mapping from previous versions of
\fBmbsync\fR. If you were using \fBisync\fR version 0.8 or 0.9.x you might \fBmbsync\fR. If you were using \fBisync\fR version 0.8 or 0.9.x you might
want to use \fBmdconvert\fR to convert the mailboxes to the more efficient want to use \fBmdconvert\fR to convert the mailboxes to the more efficient
\fBnative\fR UID storage scheme after migrating them. \fBnative\fR UID storage scheme after migrating them.
.br
\fBisync\fR is deprecated. Please use the \fB-w\fR option to permanently
migrate the configuration and start using \fBmbsync\fR directly.
.. ..
.SH OPTIONS .SH OPTIONS
.TP .TP

View File

@ -288,6 +288,9 @@ main( int argc, char **argv )
} }
} }
if (!writeout)
fputs( "Notice: please run 'isync -w' and start using 'mbsync' directly.\n", stderr );
if (config) { if (config) {
if (*config != '/') { if (*config != '/') {
if (!getcwd( path1, sizeof(path1) )) { if (!getcwd( path1, sizeof(path1) )) {