>> I like the others though, though in applying them I ran into some
>> trouble, partly through my adding lines near the top of the file that
>> change line numbers and seemed to confuse git. So they are now applied
>> to a local copy, but in my name (but with your commit messages).
>
> What comman
Excerpts from Hamish D's message of 2011-02-17 19:45:20 +0100:
> > While reimporting all my messages I encountered a few problemes with
> > the GPGME code. Please consider the attached fixes.
>
> 0001-Encode-multipart-messages-for-crypt-operations.patch already
> appears to be in master ...
Yes t
> While reimporting all my messages I encountered a few problemes with
> the GPGME code. Please consider the attached fixes.
0001-Encode-multipart-messages-for-crypt-operations.patch already
appears to be in master ...
I like the others though, though in applying them I ran into some
trouble, par
Hi
While reimporting all my messages I encountered a few problemes with
the GPGME code. Please consider the attached fixes.
The second patch depends on the first (error message unification). But
if you don't like the first I can easily produce a standalone version.
Gaudenz
--
Ever tried. Ever
Hi
While reimporting all my messages to recreate the index I fixed a few
message parsing issues. Please consider the attached patches against
master.
Gaudenz
--
Ever tried. Ever failed. No matter.
Try again. Fail again. Fail better.
~ Samuel Beckett ~
0001-Don-t-normalize_whitespace-message-r
HI
Excerpts from Gaudenz Steinlin's message of 2011-02-09 22:27:13 +0100:
> Hi
>
> While debuging the trackeback posted below I discovered that my xapian
> index contains some of the message snippets in ASCII-8BIT and others
> in UTF-8. This leads to probelems when building the thread-view for
>
