Browse Source

fix typos

1.1
Oswald Buddenhagen 11 years ago
parent
commit
1c758be695
  1. 4
      src/mbsync.1

4
src/mbsync.1

@ -199,7 +199,7 @@ versions 0.8 and 0.9.x. The invariant parts of the file names of the messages
are used as keys into a Berkeley database named .isyncuidmap.db, which holds are used as keys into a Berkeley database named .isyncuidmap.db, which holds
the UID validity as well. the UID validity as well.
.br .br
The \fBnative\fR scheme is faster, more space efficient, endianess independent The \fBnative\fR scheme is faster, more space efficient, endianness independent
and "human readable", but will be disrupted if a message is copied from another and "human readable", but will be disrupted if a message is copied from another
mailbox without getting a new file name; this would result in duplicated UIDs mailbox without getting a new file name; this would result in duplicated UIDs
sooner or later, which in turn results in a UID validity change, making sooner or later, which in turn results in a UID validity change, making
@ -439,7 +439,7 @@ Store are marked as deleted only, i.e., they won't be really deleted until
that Store is expunged. that Store is expunged.
.br .br
\fBFlags\fR - propagate flag changes. Note that Deleted/Trashed is a flag as \fBFlags\fR - propagate flag changes. Note that Deleted/Trashed is a flag as
well; this is particularily interesting if you use \fBmutt\fR with the well; this is particularly interesting if you use \fBmutt\fR with the
maildir_trash option. maildir_trash option.
.br .br
\fBAll\fR (\fB--full\fR on the command line) - all of the above. \fBAll\fR (\fB--full\fR on the command line) - all of the above.

Loading…
Cancel
Save