Issue 2550874
Created on 2015-03-03 00:52 by jerrykan, last changed 2015-03-19 13:01 by jerrykan.
|
| msg5244 |
Author: [hidden] (jerrykan) |
Date: 2015-03-03 00:52 |
|
Not sure of the historical reasons for having the rfc2822 module, but it
seems like it could be removed with minimal impact.
|
| msg5245 |
Author: [hidden] (jerrykan) |
Date: 2015-03-03 01:29 |
|
A majority of the module is not being used, and the one function that is
being used can easily be replicated in mailgw.py, meaning that
everything related to the rfc2822 module can be removed.
|
| msg5248 |
Author: [hidden] (ber) |
Date: 2015-03-03 09:01 |
|
On Tuesday 03 March 2015 at 01:52:21, John Kristensen wrote:
> Not sure of the historical reasons for having the rfc2822 module
In the comment it says that it added functions that rfc822 was missing at the
time.
|
| msg5251 |
Author: [hidden] (jerrykan) |
Date: 2015-03-03 13:27 |
|
This commit message seems to pretty much confirm that the module is much
not really used any more:
http://hg.code.sf.net/p/roundup/code/rev/1ebab2e397d0
|
| msg5294 |
Author: [hidden] (jerrykan) |
Date: 2015-03-19 13:01 |
|
Patch has been committed:
http://hg.code.sf.net/p/roundup/code/rev/7f8f27ce1a06
|
|
| Date |
User |
Action |
Args |
| 2015-03-19 13:01:05 | jerrykan | set | status: new -> closed
messages:
+ msg5294 |
| 2015-03-03 13:27:55 | jerrykan | set | messages:
+ msg5251 |
| 2015-03-03 09:01:34 | ber | set | nosy:
+ ber
messages:
+ msg5248 |
| 2015-03-03 01:33:15 | jerrykan | link | issue2550870 dependencies |
| 2015-03-03 01:29:50 | jerrykan | set | keywords:
+ patch
files:
+ issue2550874-1.patch
messages:
+ msg5245 |
| 2015-03-03 00:52:21 | jerrykan | create | |
|