mailman2 - mirror of https://code.launchpad.net/~mailman-coders/mailman/2.1

	Commit message (Collapse)	Author	Age	Files	Lines
*	FSF office has moved to 51 Franklin Street.	tkikuchi	2005-08-27	1	-1/+1
\|
*	I finally find out why re.escape() doesn't work properly. '%' should not	tkikuchi	2005-05-13	1	-8/+8
\| \| \| \| \|	be escaped for it is the insert directive. It was my trial and error in the comments in previous version. Well, I didn't think of '++' ...
*	prefix_subject(): Don't double escape the prefix_pattern.	bwarsaw	2005-05-13	1	-3/+0
\|
*	strip_subject() in HyperArch.py	bwarsaw	2005-05-13	1	-8/+7
\| \| \| \| \| \| \| \| \| \|	prefix_subject() in CookHeaders.py When calling re.sub() to substitute the subject prefix, you have to escape the pattern, otherwise prefixes like [C++] cause "multiple repeat" exceptions in re. Also, whitespace normalization and copyright years updates.
*	Request from Brad Knowles. We need subject prefix stripped	tkikuchi	2005-02-12	1	-0/+11
\| \| \| \|	from the posts from mailling list for gatewaying to nntp.
*	bumping 2.1.6b3	tkikuchi	2005-02-11	1	-1/+4
\|
*	Fix in pipermail to use Unicode for indexing (sort fails for ascii 8bit)	tkikuchi	2005-01-25	1	-1/+1
\| \| \| \|	with some code clean up. Also, include SV (danish/swedish) Re: like pattern.
*	Introduce old_style in CookHeaders.py and OLD_STYLE_PREFIXING in Defaults.py.	tkikuchi	2005-01-22	1	-5/+29
\| \| \| \| \|	Now the default behavior of prefixing is "Re: [prefix] subject". Variations like "Re[2]:" and German style "AW:" is now replaced by "Re:".
*	[ 601117 ] add sequencial number in subject prefix	tkikuchi	2004-10-09	1	-52/+117
\| \| \| \|	Here is my major patch. It was postponed to 2.2 but since 2.2 is so late...
*	Fix comment	bwarsaw	2003-12-18	1	-2/+1
\|
*	uheader(): Added default argument for maxlinelen.	bwarsaw	2003-12-18	1	-11/+12
\| \| \| \| \| \| \| \| \| \|	process(): Reworked the way we calculate the List-Id header in the face of i18n descriptions which may need to be quoted (if ASCII and containing RFC 2822 special chars). What we do now is RFC 2047 encode just the description part, if there is one, then use formataddr() to combine that with the email address-like list identification.
*	process(): Quote the description when adding it to the List-ID header,	bwarsaw	2003-12-13	1	-1/+1
\| \| \| \| \|	in case there are any special characters (in the RFC 2822) in the description.
*	Backporting from the HEAD -- updated handlers	bwarsaw	2003-09-22	1	-1/+1
\|
*	Backporting from trunk	bwarsaw	2003-03-31	1	-2/+2
\|
*	Backporting from the trunk.	bwarsaw	2003-02-08	1	-5/+14
\|
*	This commit was manufactured by cvs2svn to create branch		2003-01-02	1	-0/+254
	'Release_2_1-maint'.