[Python-bugs-list] [Bug #125610] SuppReq: please elaborate on your email notif. requests

[noreply@sourceforge.net]

Bug #125610, was updated on 2000-Dec-13 05:34
Here is a current snapshot of the bug.

Project: Python
Category: None
Status: Open
Resolution: None
Bug Group: Not a Bug
Priority: 5
Submitted by: pfalcon
Assigned to : nobody
Summary: SuppReq: please elaborate on your email notif. requests

Details: We've got the task "Python requests"
http://sourceforge.net/pm/task.php?func=detailtask&project_task_id=22577&group_id=1&group_project_id=2 . I believe bigdisk knows what that means but I think I could do that faster, so I'd like to have information from the original source. Please give specific examples how you want it to be. Thanks.


Follow-Ups:

Date: 2000-Dec-13 06:20
By: gvanrossum

Comment:
OK, I'll clarify.  Note that this applies both to the patch and the bugs products.

1. Word wrap: the comments entered in the database for bugs & patches are often entered with a single very long line per paragraph.  When the notification email is sent out, most Unix mail readers don't wrap words correctly.  The request is to break any line that is longer than 79 characters in shorter pieces, the way e.g. ESC-q does in Emacs, or the fmt(1) program.

2. clickable submitter name: in the patch or bug details page, the submitter ("Submitted By" field) should be a hyperlink to the developer profile for that user (except if it is Nobody, of course).

3. mention what changed in the email: it would be nice if at the top of the notification email it said what caused the mail to be sent, e.g. "status changed from XXX to YYY" or "assiged to ZZZ" or "new comment added by XXX" or "new patch uploaded" or "priority changed to QQQ".  If more than one field changed they should all be summarized.

Hope this helps!  Thanks for doing this.  We love our SourceForge!
-------------------------------------------------------

For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=125610&group_id=5470