From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Cc: David Bremner <bremner@debian.org>
Subject: [PATCH 1/2] notmuch.1: typo fixes new wording for dump/restore
Date: Fri, 21 Oct 2011 19:21:13 -0300 [thread overview]
Message-ID: <1319235674-7047-1-git-send-email-david@tethera.net> (raw)
In-Reply-To: <1319226477-4181-7-git-send-email-david@tethera.net>
From: David Bremner <bremner@debian.org>
These changes were included in Thomas's restore --accumulate patch,
but are actually more generally applicable.
---
notmuch.1 | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/notmuch.1 b/notmuch.1
index 10ed32e..4f864a8 100644
--- a/notmuch.1
+++ b/notmuch.1
@@ -454,7 +454,7 @@ section below for details of the supported syntax for <search-terms>.
The
.BR dump " and " restore
commands can be used to create a textual dump of email tags for backup
-purposes, and to restore from that dump
+purposes, and to restore from that dump.
.RS 4
.TP 4
@@ -483,7 +483,9 @@ section below for details of the supported syntax for <search-terms>.
.BR restore " <filename>"
Restores the tags from the given file (see
-.BR "notmuch dump" "."
+.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.
--
1.7.6.3
next prev parent reply other threads:[~2011-10-21 22:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 19:07 [PATCH] notmuch restore --accumulate Thomas Schwinge
2011-09-05 19:31 ` Jameson Graef Rollins
2011-09-09 9:06 ` Louis Rilling
2011-09-09 9:45 ` Thomas Schwinge
2011-09-09 16:13 ` Austin Clements
2011-09-09 17:22 ` Thomas Schwinge
2011-09-09 17:35 ` Austin Clements
2011-09-09 18:58 ` Jameson Graef Rollins
2011-09-29 18:24 ` [PATCH] patchformatting: Test Suite Enhancements Thomas Schwinge
2011-09-29 17:36 ` [PATCH, v2] notmuch restore --accumulate Thomas Schwinge
2011-09-29 17:37 ` Thomas Schwinge
2011-10-21 19:47 ` Updated v3 patches for " David Bremner
2011-10-21 19:47 ` [PATCH 1/6] test/test-lib.sh: update comments David Bremner
2011-10-21 19:47 ` [PATCH 2/6] test/dump-restore: expand test suite for dump-restore, make more robust David Bremner
2011-10-21 19:47 ` [PATCH 3/6] test/dump-restore: add tests for restore --accumulate David Bremner
2011-10-21 19:47 ` [PATCH 4/6] notmuch-restore: implement --accumulate option David Bremner
2011-10-21 19:47 ` [PATCH 5/6] test/dump-restore: Fix quoting on grep David Bremner
2011-10-21 19:47 ` [PATCH 6/6] notmuch-restore: check for extra arguments David Bremner
2011-10-21 22:21 ` David Bremner [this message]
2011-10-21 22:21 ` [PATCH 2/2] docs: Update news, man page, and online help for restore --accumulate David Bremner
2011-10-23 19:50 ` Updated v3 patches for notmuch " David Bremner
2011-10-16 21:48 ` [PATCH, v2] " David Bremner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1319235674-7047-1-git-send-email-david@tethera.net \
--to=david@tethera.net \
--cc=bremner@debian.org \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).