David Bremner writes:
>
> I'm marking this bug as fixed; feel free to let us know of any problems
> with the new batch-tag format.
I should say I mean the bug with message-ids with spaces in
them. Performance issues with notmuch new (and particularly, bad
prediction of completion times) remain,
Petter Reinholdtsen writes:
> Running 'notmuch restore' to get my tags back took 106 minutes, and I
> was very surprised that the restore could not load all the tags stored
> by 'notmuch dump'. The restore complained about this line:
>
> NO*TELEMAX**NORWAYII M0018001012307699038 (unread usit
Petter Reinholdtsen p...@hungry.com writes:
Running 'notmuch restore' to get my tags back took 106 minutes, and I
was very surprised that the restore could not load all the tags stored
by 'notmuch dump'. The restore complained about this line:
NO*TELEMAX**NORWAYII M0018001012307699038
David Bremner brem...@unb.ca writes:
I'm marking this bug as fixed; feel free to let us know of any problems
with the new batch-tag format.
I should say I mean the bug with message-ids with spaces in
them. Performance issues with notmuch new (and particularly, bad
prediction of completion
Quoth Petter Reinholdtsen on Nov 21 at 11:35 pm:
> The indexing took 36 hours. At the start it claimed it would take 10
> hours, and it continued to underestimate the amount of time left until
> the very end. It claimed to have 1 hour left when I checked before I
> went to bed, and claimed to
On Mon, 21 Nov 2011 23:35:34 +0100, Petter Reinholdtsen
wrote:
>
> NO*TELEMAX**NORWAYII M0018001012307699038 (unread usit year-2002)
>
> The message in question is a bounce from some X400 mail system, and its
> message id look like this:
>
> Message-Id:
This weekend up updated my notmuch version to the 0.10 rc2 version
available in Debian/unstable, and made a few observations I would like
to share. I rebuilt the source on Debian/Squeeze to get it working for
the machine I use to read email, and patched it to get the unsorted dump
before