Jani Nikula wrote:
> It seems to be list mail. It would not surprise me that some ill-advised
> mailing list manager would decode and re-encode the subject. One could
> try sending the same message directly and through the list, and see if
> there's a difference.
Possibly, though I don't have the
On Sun, 10 Feb 2013, Albin Stjerna wrote:
> Hm. So I should report this to Thunderbird? I tried searching through
> their bug reports but didn't find anything.
I tried that too; there were other RFC 2047 related header bugs but
could not find this one. And the other bugs were old and fixed. Judgi
A little bug-fix to learn how to contribute to nutmuch, this time a combined
commit with git rebase to provide one patch from 15.1.
---
lib/query.cc | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/lib/query.cc b/lib/query.cc
index e9c1a2d..7381a54 100644
--- a/lib
>From many replies I understand manual thread-joining and -breaking exists with
>mutt's manual commands and default subject breaking -as Gmail does- would not
>be preferred, while not only version control systems vary subjects within a
>thread, but also discussions with slight off-topic forks an
On Sun, 10 Feb 2013, Albin Stjerna wrote:
> Hm. So I should report this to Thunderbird? I tried searching through
> their bug reports but didn't find anything.
I tried that too; there were other RFC 2047 related header bugs but
could not find this one. And the other bugs were old and fixed. Judgi
David/Austin,
I sent it as a patch to my previous patch. Is that correct, or should I first
'revert' the file to 15.1?
Robert
-Oorspronkelijk bericht-
Van: David Bremner [mailto:david at tethera.net]
Verzonden: zondag 10 februari 2013 2:17
Aan: notmuch at notmuchmail.org
CC: Robert Mas
---
lib/query.cc | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/lib/query.cc b/lib/query.cc
index 046663a..7381a54 100644
--- a/lib/query.cc
+++ b/lib/query.cc
@@ -39,12 +39,12 @@ typedef struct _notmuch_mset_messages {
} notmuch_mset_messages_t;
struct _notmuc
Jani Nikula wrote:
> It seems to be list mail. It would not surprise me that some ill-advised
> mailing list manager would decode and re-encode the subject. One could
> try sending the same message directly and through the list, and see if
> there's a difference.
Possibly, though I don't have the
Robert Mast writes:
> David/Austin,
>
> I sent it as a patch to my previous patch. Is that correct, or should I first
> 'revert' the file to 15.1?
>
> Robert
Hi Robert;
I didn't see any followup patch from you on the list; can you tell me the
message-id?
In any case, in general you should sen
Jani Nikula wrote:
> Is that entirely on one line in the original message file? If not, where
> exactly is it split?
It's in one line.
> Either way, at a glance, it seems like the encoding is malformed. I
> think the encoded-word ("=?" charset "?" encoding "?" encoded-text "?=")
> should be sepa
On Sun, Feb 10 2013, Jani Nikula wrote:
> nmbug pull only merges upstream master, but nmbug push tries to push
> all local branches. The asymmetry results in conflicts whenever there
> have been changes in the config branch in the origin:
>
> $ nmbug push
> To nmbug at nmbug.tethera.net:nmbug-tag
nmbug pull only merges upstream master, but nmbug push tries to push
all local branches. The asymmetry results in conflicts whenever there
have been changes in the config branch in the origin:
$ nmbug push
To nmbug at nmbug.tethera.net:nmbug-tags
! [rejected]config -> config (non-fast-for
Jani Nikula wrote:
> Is that entirely on one line in the original message file? If not, where
> exactly is it split?
It's in one line.
> Either way, at a glance, it seems like the encoding is malformed. I
> think the encoded-word ("=?" charset "?" encoding "?" encoded-text "?=")
> should be sepa
13 matches
Mail list logo
