From 00e5d4b6f8f9357e1d0da2c5eb7b4b9ec043ec3b Mon Sep 17 00:00:00 2001 From: Florian Friesdorf Date: Tue, 26 Apr 2011 21:55:02 +0200 Subject: [PATCH] performance: format fixes --- performance.mdwn | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/performance.mdwn b/performance.mdwn index aa1029b..e686cab 100644 --- a/performance.mdwn +++ b/performance.mdwn @@ -22,17 +22,17 @@ database format, but also used in case of `chert`. XXX: add examples -2. Backup your notmuch tags +2. Backup your notmuch tags: $ cd $ notmuch dump notmuch-dump-b4chert -3. Move away your old database +3. Move away your old database: $ mv $(notmuch config get database.path)/.notmuch/ notmuch-db-b4chert 4. Find and import your messages, a new and fresh database will be -created. +created: $ XAPIAN_PREFER_CHERT=1 notmuch new @@ -44,23 +44,23 @@ somebody more knowledgeable. After the initial import it is definitely not necessary to define `XAPIAN_PREFER_CHERT` for subsequent calls of `notmuch new`. -5. Restore your tags +5. Restore your tags: $ notmuch restore notmuch-dump-b4chert -6. Check whether you are on chert now. +6. Check whether you are on chert now: $ ls $(notmuch config get database.path)/.notmuch/xapian/iam* iamchert -If it says `iamflint`, most likely you are still using xapian 1.0.x. + If it says `iamflint`, most likely you are still using xapian 1.0.x. 7. Clean-up If you are sure everything is fine, you can delete the old things. The dump of your tags you might want to keep anyway as a backup - on the other hand you should have some mechanism in place to make regular -backups of your notmuch database. +backups of your notmuch database: $ rm notmuch-dump-b4chert $ rm -R notmuch-db-b4chert -- 2.43.0