<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mailman.git/src/mailman/rest, branch master</title>
<subtitle>The GNU Mailing List manager.
</subtitle>
<id>https://git.neuromancer.sk/mailman.git/atom?h=master</id>
<link rel='self' href='https://git.neuromancer.sk/mailman.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.neuromancer.sk/mailman.git/'/>
<updated>2017-08-30T02:51:58Z</updated>
<entry>
<title>Squashed commit of the following:</title>
<updated>2017-08-30T02:51:58Z</updated>
<author>
<name>Barry Warsaw</name>
</author>
<published>2017-08-30T02:51:58Z</published>
<link rel='alternate' type='text/html' href='https://git.neuromancer.sk/mailman.git/commit/?id=057bc0704ab6d975e327c11cac204decfb478c4d'/>
<id>urn:sha1:057bc0704ab6d975e327c11cac204decfb478c4d</id>
<content type='text'>
commit 3c6500c2292869f94667520f16c8d6c6f1d2c530
Author: Barry Warsaw &lt;barry@python.org&gt;
Date:   Tue Aug 29 22:51:18 2017 -0400

    Close #383

    Messages with badly encoded ``Subject`` headers no longer crash the message
    moderation REST API.

commit f6040ec139bcccd48cfa9acc734cd528a8ede35c
Author: Aurélien Bompard &lt;aurelien@bompard.org&gt;
Date:   Thu Jul 27 00:52:05 2017 +0200

    Fix #383: email encoding errors can crash the REST API
</content>
</entry>
<entry>
<title>PR288 vetted</title>
<updated>2017-08-29T14:07:54Z</updated>
<author>
<name>Barry Warsaw</name>
</author>
<published>2017-08-29T14:07:54Z</published>
<link rel='alternate' type='text/html' href='https://git.neuromancer.sk/mailman.git/commit/?id=ae0042a90220119414f61aeb20c6b58bfacb8af2'/>
<id>urn:sha1:ae0042a90220119414f61aeb20c6b58bfacb8af2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Rename metadata key for clarity</title>
<updated>2017-08-04T01:13:04Z</updated>
<author>
<name>Barry Warsaw</name>
</author>
<published>2017-08-04T01:13:04Z</published>
<link rel='alternate' type='text/html' href='https://git.neuromancer.sk/mailman.git/commit/?id=9cdcffbc1189a19bc2963cf3d5c86a3d4f1f24a6'/>
<id>urn:sha1:9cdcffbc1189a19bc2963cf3d5c86a3d4f1f24a6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Convert to click for CLI options</title>
<updated>2017-07-22T03:02:05Z</updated>
<author>
<name>Barry Warsaw</name>
</author>
<published>2017-07-22T03:02:05Z</published>
<link rel='alternate' type='text/html' href='https://git.neuromancer.sk/mailman.git/commit/?id=f00b94f18e1d82d1488cbcee6053f03423bc2f49'/>
<id>urn:sha1:f00b94f18e1d82d1488cbcee6053f03423bc2f49</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'doc-UTF8' into 'master'</title>
<updated>2017-05-25T01:04:33Z</updated>
<author>
<name>Barry Warsaw</name>
</author>
<published>2017-05-25T01:04:33Z</published>
<link rel='alternate' type='text/html' href='https://git.neuromancer.sk/mailman.git/commit/?id=6fb8bbbec1f8cc86e91002402b365bd1753d087a'/>
<id>urn:sha1:6fb8bbbec1f8cc86e91002402b365bd1753d087a</id>
<content type='text'>
Document Unicode usage in Mailman 3 REST API and email addresses.

See merge request !274</content>
</entry>
<entry>
<title>Fixup ref spacing.</title>
<updated>2017-05-24T23:14:43Z</updated>
<author>
<name>Stephen J. Turnbull</name>
</author>
<published>2017-05-24T23:14:43Z</published>
<link rel='alternate' type='text/html' href='https://git.neuromancer.sk/mailman.git/commit/?id=674276a3d0404544bd5da74c8a2f2daa8174af40'/>
<id>urn:sha1:674276a3d0404544bd5da74c8a2f2daa8174af40</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Fix the template name of the welcome message.</title>
<updated>2017-05-24T20:25:26Z</updated>
<author>
<name>Barry Warsaw</name>
</author>
<published>2017-05-24T20:25:26Z</published>
<link rel='alternate' type='text/html' href='https://git.neuromancer.sk/mailman.git/commit/?id=b2d961dcffa6602c2b39e421b157c0c0026b6c46'/>
<id>urn:sha1:b2d961dcffa6602c2b39e421b157c0c0026b6c46</id>
<content type='text'>
We did not previously complete the renaming of the templates.  Rename:

* user:ack:welcome -&gt; list:user:notice:welcome
* user:ack:goodbye -&gt; list:user:notice:goodbye

The new names are what are actually used in send_welcome_message() and
send_goodbye_message() so the old names were actually never used.

NOTE: If you added welcome or goodbye templates through REST from git head,
the old names will not be used.  Given that this wasn't a feature in 3.0, and
the above use case is very unlikely, I've decided not to do a migration.  If
anybody is affected, the changes can be made manually in withlist.

Closes: #337
</content>
</entry>
<entry>
<title>Document Unicode usage in Mailman 3 REST API and email addresses.</title>
<updated>2017-05-24T08:39:03Z</updated>
<author>
<name>Stephen J. Turnbull</name>
</author>
<published>2017-05-24T01:25:03Z</published>
<link rel='alternate' type='text/html' href='https://git.neuromancer.sk/mailman.git/commit/?id=95c9f8f3e13f922baa1200dcbe909da751e27652'/>
<id>urn:sha1:95c9f8f3e13f922baa1200dcbe909da751e27652</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add self_links to the system configuration resources.</title>
<updated>2017-05-23T19:39:39Z</updated>
<author>
<name>Barry Warsaw</name>
</author>
<published>2017-05-23T19:32:03Z</published>
<link rel='alternate' type='text/html' href='https://git.neuromancer.sk/mailman.git/commit/?id=3bd2a292b7300ce354de1ed405dc8665311acd9f'/>
<id>urn:sha1:3bd2a292b7300ce354de1ed405dc8665311acd9f</id>
<content type='text'>
Closes #335
</content>
</entry>
<entry>
<title>Update welcome template with correct password reset instructions</title>
<updated>2017-05-22T17:04:19Z</updated>
<author>
<name>Britt Gresham</name>
</author>
<published>2017-05-22T16:59:44Z</published>
<link rel='alternate' type='text/html' href='https://git.neuromancer.sk/mailman.git/commit/?id=efe56d6ed33012c51ce2c4980c4555ec6321ee30'/>
<id>urn:sha1:efe56d6ed33012c51ce2c4980c4555ec6321ee30</id>
<content type='text'>
Before this commit the welcome template included older instructions on
how to reset a users password.

This commit updates the documentation to reflect the new way of
resetting a users password by clicking on a link when logging in.
</content>
</entry>
</feed>
