- <b>--accumulate</b>
-
- The union of the existing and new tags is applied, instead
- of replacing each message's tags as they are read in from
- the dump file.
-
- <b>--format=(sup|batch-tag|auto)</b>
-
- Notmuch restore supports two plain text dump formats, with
- each line specifying a message-id and a set of tags. For
- details of the actual formats, see <a href='../notmuch-dump-1/'>notmuch-dump</a>(1).
-
- <b>sup</b>
-
- The <b>sup</b> dump file format is specifically chosen to be
- compatible with the format of files produced by
- sup-dump. So if you've previously been using sup for
- mail, then the <b>notmuch</b> <b>restore</b> command provides you a
- way to import all of your tags (or labels as sup
- calls them).
-
- <b>batch-tag</b>
-
- The <b>batch-tag</b> dump format is intended to more robust
- against malformed message-ids and tags containing
- whitespace or non-<b>ascii</b>(7) characters. See <a href='../notmuch-dump-1/'>not-</a>
- <a href='../notmuch-dump-1/'>much-dump</a>(1) for details on this format.
-
- <b>notmuch</b> <b>restore</b> updates the maildir flags according
- to tag changes if the <b>maildir.synchronize</b>_<b>flags</b> con-
- figuration option is enabled. See <a href='../notmuch-config-1/'>notmuch-config</a>(1)
- for details.
-
- <b>auto</b>
-
- This option (the default) tries to guess the format
- from the input. For correctly formed input in either
- supported format, this heuristic, based the fact that
- batch-tag format contains no parentheses, should be
- accurate.
+ <b>--accumulate</b>
+ The union of the existing and new tags is applied, instead of
+ replacing each message's tags as they are read in from the dump
+ file.
+
+ <b>--format=(sup|batch-tag|auto)</b>
+ Notmuch restore supports two plain text dump formats, with each
+ line specifying a message-id and a set of tags. For details of
+ the actual formats, see <a href='../notmuch-dump-1/'>notmuch-dump</a>(1).
+
+ <b>sup</b> The <b>sup</b> dump file format is specifically chosen to be
+ compatible with the format of files produced by sup-dump.
+ So if you've previously been using sup for mail, then the
+ <b>notmuch</b> <b>restore</b> command provides you a way to import all
+ of your tags (or labels as sup calls them).
+
+ <b>batch-tag</b>
+ The <b>batch-tag</b> dump format is intended to more robust
+ against malformed message-ids and tags containing white‐
+ space or non-<b>ascii</b>(7) characters. See <a href='../notmuch-dump-1/'>notmuch-dump</a>(1) for
+ details on this format.
+
+ <b>notmuch</b> <b>restore</b> updates the maildir flags according to
+ tag changes if the <b>maildir.synchronize</b>_<b>flags</b> configura‐
+ tion option is enabled. See <a href='../notmuch-config-1/'>notmuch-config</a>(1) for
+ details.
+
+ <b>auto</b> This option (the default) tries to guess the format from
+ the input. For correctly formed input in either supported
+ format, this heuristic, based the fact that batch-tag
+ format contains no parentheses, should be accurate.
+
+ <b>--include=(config|properties|tags)</b>
+ Control what kind of metadata is restored.
+
+ <b>config</b> Restore configuration data to the database. Each configu‐
+ ration line starts with "#@ ", followed by a space sepa‐
+ rated key-value pair. Both key and value are hex encoded
+ if needed.
+
+ <b>properties</b>
+ Restore per-message (key,value) metadata. Each line
+ starts with "#= ", followed by a message id, and a space
+ separated list of key=value pairs. Ids, keys and values
+ are hex encoded if needed. See <a href='../notmuch-properties-7/'>notmuch-properties</a>(7) for
+ more details.
+
+ <b>tags</b> Restore per-message metadata, namely tags. See <u>format</u>
+ above for more details.
+
+ The default is to restore all available types of data. The
+ option can be specified multiple times to select some subset.
+
+ <b>--input=<filename></b>
+ Read input from given file instead of stdin.