unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
blob 2191df016353508731704c5793b747b2bc1616fb 1211 bytes (raw)
name: man/man1/notmuch-restore.1 	 # note: path name is non-authoritative(*)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
 
.TH NOTMUCH-RESTORE 1 2011-12-04 "Notmuch 0.10.2"
.SH NAME
notmuch-restore \- Restores the tags from the given file (see notmuch dump).

.SH SYNOPSIS

.B "notmuch restore"
.RB [ "--accumulate" ]
.RI "[ <" filename "> ]"

.SH DESCRIPTION

Restores the tags from the given file (see
.BR "notmuch dump" ")."

The input is read from the given filename, if any, or from stdin.

Note: The 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 restore"
command provides you a way to import all of your tags (or labels as
sup calls them).

The --accumulate switch causes the union of the existing and new tags to be
applied, instead of replacing each message's tags as they are read in from the
dump file.

See \fBnotmuch-search-terms\fR(7)
for details of the supported syntax for <search-terms>.

.RE
.SH SEE ALSO

\fBnotmuch\fR(1), \fBnotmuch-config\fR(1), \fBnotmuch-count\fR(1),
\fBnotmuch-hooks\fR(5), \fBnotmuch-new\fR(1), \fBnotmuch-part\fR(1),
\fBnotmuch-reply\fR(1), \fBnotmuch-dump\fR(1),
\fBnotmuch-search\fR(1), \fBnotmuch-search-terms\fR(7),
\fBnotmuch-show\fR(1), \fBnotmuch-tag\fR(1)

debug log:

solving 2191df0 ...
found 2191df0 in https://yhetil.org/notmuch.git/

(*) Git path names are given by the tree(s) the blob belongs to.
    Blobs themselves have no identifier aside from the hash of its contents.^

Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).