<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/notmuch-reply.c, branch 0.2</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.2</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.2'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2010-04-13T16:23:54Z</updated>
<entry>
<title>Decode headers in reply</title>
<updated>2010-04-13T16:23:54Z</updated>
<author>
<name>Michal Sojka</name>
<email>sojkam1@fel.cvut.cz</email>
</author>
<published>2010-03-03T07:50:56Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=452fbedcd5db101378b01c957a7f0574eb708afc'/>
<id>urn:sha1:452fbedcd5db101378b01c957a7f0574eb708afc</id>
<content type='text'>
When headers contain non-ASCII characters, they are encoded according
to rfc2047. Nomtuch reply command emits the headers in the encoded
form, which makes them hard to read by humans who compose the reply.

For example instead of "Subject: Re: Rozlučka" one currently sees
"Subject: Re: =?iso-8859-2?q?Rozlu=E8ka?=".

This patch adds a new GMime filter which is used to decode headers to
UTF-8 and uses this filter when notmuch reply outputs headers.

Signed-off-by: Michal Sojka &lt;sojkam1@fel.cvut.cz&gt;
</content>
</entry>
<entry>
<title>Fix code extracting the MTA from Received: headers</title>
<updated>2010-04-07T22:36:40Z</updated>
<author>
<name>Dirk Hohndel</name>
<email>hohndel@infradead.org</email>
</author>
<published>2010-04-07T20:38:29Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=569ecf8c164fe4732aee4296c956ecf6b8575b6c'/>
<id>urn:sha1:569ecf8c164fe4732aee4296c956ecf6b8575b6c</id>
<content type='text'>
The previous code made too many assumptions about the (sadly not
standardized) format of the Received headers. This version should
be more robust to deal with different variations.

Signed-off-by: Dirk Hohndel &lt;hohndel@infradead.org&gt;
</content>
</entry>
<entry>
<title>notmuch-reply: Remove stray brace.</title>
<updated>2010-04-07T14:17:12Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-04-07T14:17:12Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=8d4fa40beccde5ec879cc05341e45b18a6cf9e0f'/>
<id>urn:sha1:8d4fa40beccde5ec879cc05341e45b18a6cf9e0f</id>
<content type='text'>
That was breaking the build.
</content>
</entry>
<entry>
<title>notmuch-reply: Remove a useless level of nesting.</title>
<updated>2010-04-07T01:51:57Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-04-07T01:50:22Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=542e32876ebae630d7a281be938296950689cb50'/>
<id>urn:sha1:542e32876ebae630d7a281be938296950689cb50</id>
<content type='text'>
Making the code a tiny bit easier to read (in my opinion at least).
</content>
</entry>
<entry>
<title>notmuch-reply: Fix some whitespace issues.</title>
<updated>2010-04-07T01:51:47Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-04-07T01:49:25Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3e216ba60d7e933a9b954aac5eaf0f5286819496'/>
<id>urn:sha1:3e216ba60d7e933a9b954aac5eaf0f5286819496</id>
<content type='text'>
No actual code change here. Just whitespace style, (mostly just my
preferred space before a left parenthesis, and a space after a comma).
</content>
</entry>
<entry>
<title>guess From address from Received headers</title>
<updated>2010-04-07T01:47:40Z</updated>
<author>
<name>Dirk Hohndel</name>
<email>hohndel@infradead.org</email>
</author>
<published>2010-04-06T19:45:57Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4fd9ea05e896e77e388f3012e619f4e805282944'/>
<id>urn:sha1:4fd9ea05e896e77e388f3012e619f4e805282944</id>
<content type='text'>
When replying to a message notmuch tries to pick the correct From
 address by looking which one of a user's configured email addresses
 were included in To or Cc headers of the email that is being replied to.
 If none of the users email addresses are in the To or Cc headers we now
 try to guess from the first (chronologically, last) Received header
 which domain this email was received in and therefore which of the
 email addresses to use in a reply
 If that fails we still use the primary email as From email

Signed-off-by: Dirk Hohndel &lt;hohndel@infradead.org&gt;
</content>
</entry>
<entry>
<title>lib: Rename iterator functions to prepare for reverse iteration.</title>
<updated>2010-03-09T17:22:29Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-03-09T17:22:29Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4e5d2f22db290a830c0267f34b519c6138af00ed'/>
<id>urn:sha1:4e5d2f22db290a830c0267f34b519c6138af00ed</id>
<content type='text'>
We rename 'has_more' to 'valid' so that it can function whether
iterating in a forward or reverse direction. We also rename
'advance' to 'move_to_next' to setup parallel naming with
the proposed functions 'move_to_first', 'move_to_last', and
'move_to_previous'.
</content>
</entry>
<entry>
<title>notmuch reply: Rename the mailing_list_munged_reply_to function</title>
<updated>2010-02-04T20:42:09Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-02-04T20:39:11Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d111c720bad53f98edba958aa605e857036a2bc8'/>
<id>urn:sha1:d111c720bad53f98edba958aa605e857036a2bc8</id>
<content type='text'>
This function detects whether the address in the Reply-To header
already appears in either To or Cc. So give it a name that reflects
what it does (reply_to_header_is_redundant) rather than the old name
which described one possible use of the function, (as a simple
heuristic for detecting whether a mailing list had applied reply-to
munging).
</content>
</entry>
<entry>
<title>notmuch reply: Prevent GMIME assertion complaints for empty Reply-to header.</title>
<updated>2010-02-04T20:42:09Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-02-04T20:32:28Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=62379f3dee5bc3673007271bc43ecc2587ac4e22'/>
<id>urn:sha1:62379f3dee5bc3673007271bc43ecc2587ac4e22</id>
<content type='text'>
Apparently, GMime doesn't want to create a valid address list object
for an empty string. That's annoying, but it's easy enough to test for
the empty string and avoid the problem.
</content>
</entry>
<entry>
<title>notmuch reply: Use strstr instead of strcasestr for portability.</title>
<updated>2010-02-04T20:42:09Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-02-04T20:29:04Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=82e47ec92b41973567f4d89bbd6afdb22fc634bd'/>
<id>urn:sha1:82e47ec92b41973567f4d89bbd6afdb22fc634bd</id>
<content type='text'>
This change was already recommended in a comment in the original
implementation of this patch. If someone really wants to support
un-munging in the case of To: and Reply-To: having the same address
but different case, then they can provide a portable approach for
that.
</content>
</entry>
</feed>
