Mercurial > p > roundup > code
comparison doc/upgrading.txt @ 6941:bd2c3b2010c3
issue2551232 - modify in-reply-to threading when multiple matches
if an email is missing an issue designator, in-reply-to threading is
attempted. In this change if in-reply-to threading matches multiple
issues, fall back to matching on subject. It used to just arbitrairly
choose the first matching issue.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Thu, 08 Sep 2022 18:49:46 -0400 |
| parents | a96a239db0d9 |
| children | d3593cbb8e6f |
comparison
equal
deleted
inserted
replaced
| 6940:3d2ec36541b9 | 6941:bd2c3b2010c3 |
|---|---|
| 166 when it opens the database, so options such as ``truncate`` | 166 when it opens the database, so options such as ``truncate`` |
| 167 are not used.) | 167 are not used.) |
| 168 | 168 |
| 169 For details on WAL mode see `<https://www.sqlite.org/wal.html>`_ | 169 For details on WAL mode see `<https://www.sqlite.org/wal.html>`_ |
| 170 and `<https://www.sqlite.org/pragma.html#pragma_journal_mode>`_. | 170 and `<https://www.sqlite.org/pragma.html#pragma_journal_mode>`_. |
| 171 | |
| 172 Change in processing of In-Reply_to email header | |
| 173 ------------------------------------------------ | |
| 174 | |
| 175 Messages received via email usually include a ``[issue23]`` | |
| 176 designator in the subject line. This indicates what issue is | |
| 177 being updated. If the designator is missing, Roundup tries | |
| 178 to find the correct issue by using the in-reply-to email | |
| 179 header. | |
| 180 | |
| 181 The former code appends the new message to the first issue | |
| 182 found with a message matching the in-reply-to | |
| 183 header. Usually a message is associated with only one | |
| 184 issue. However nothing in Roundup requires that. | |
| 185 | |
| 186 In this release, the in-reply-to matching is disabled if | |
| 187 there are multiple issues with the same message. In this | |
| 188 case, subject matching is used to try to find the matching | |
| 189 issue. | |
| 190 | |
| 191 If you don't have messages assigned to multiple issues you | |
| 192 will see no change. If you do have multi-linked messages | |
| 193 this will hopefully result in better message->issue | |
| 194 matching. | |
| 171 | 195 |
| 172 .. index:: Upgrading; 2.1.0 to 2.2.0 | 196 .. index:: Upgrading; 2.1.0 to 2.2.0 |
| 173 | 197 |
| 174 Migrating from 2.1.0 to 2.2.0 | 198 Migrating from 2.1.0 to 2.2.0 |
| 175 ============================= | 199 ============================= |