Showing content from http://mail.python.org/pipermail/python-dev/attachments/20110301/7e151485/attachment.html below:
<div dir="ltr">The PEP (<a href="http://www.python.org/dev/peps/pep-0385/">http://www.python.org/dev/peps/pep-0385/</a>) says in "Timeline":<br><br>2010-03-05: final conversion (tentative)<br><br>I assume 2011-03-05 is meant here.<br>
<br>Eli<br><br><br><br><br><br><div class="gmail_quote">On Mon, Feb 28, 2011 at 20:22, antoine.pitrou <span dir="ltr"><<a href="mailto:python-checkins@python.org">python-checkins@python.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Author: antoine.pitrou<br>
Date: Mon Feb 28 19:22:36 2011<br>
New Revision: 88676<br>
<br>
Log:<br>
Update PEP 385 with latest hooks work<br>
<br>
<br>
<br>
Modified:<br>
peps/trunk/pep-0385.txt<br>
<br>
Modified: peps/trunk/pep-0385.txt<br>
==============================================================================<br>
--- peps/trunk/pep-0385.txt (original)<br>
+++ peps/trunk/pep-0385.txt Mon Feb 28 19:22:36 2011<br>
@@ -262,7 +262,22 @@<br>
on every build slave for the branch in which the changeset occurs.<br>
<br>
The `hooks repository`_ contains ports of these server-side hooks to<br>
-Mercurial. One additional hook could be beneficial:<br>
+Mercurial, as well as a couple additional ones:<br>
+<br>
+* check branch heads: a hook to reject pushes which create a new head on<br>
+ an existing branch. The pusher then has to merge the superfetatory heads<br>
+ and try pushing again.<br>
+<br>
+* check branches: a hook to reject all changesets not on an allowed named<br>
+ branch. This hook's whitelist will have to be updated when we want to<br>
+ create new maintenance branches.<br>
+<br>
+* check line endings: a hook, based on the `eol extension`_, to reject all<br>
+ changesets committing files with the wrong line endings. The commits then<br>
+ have to be stripped and redone, possibly with the `eol extension`_ enabled<br>
+ on the comitter's computer.<br>
+<br>
+One additional hook could be beneficial:<br>
<br>
* check contributors: in the current setup, all changesets bear the<br>
username of committers, who must have signed the contributor<br>
@@ -285,9 +300,8 @@<br>
information is kept in a versioned file called ``.hgeol``, and such a<br>
file has already been checked into the Subversion repository.<br>
<br>
-A hook on the server side that turns down any changegroup or changeset<br>
-introducing inconsistent newline data can still be implemented, if<br>
-deemed necessary.<br>
+A hook also exists on the server side to reject any changeset<br>
+introducing inconsistent newline data (see above).<br>
<br>
.. _eol extension: <a href="http://mercurial.selenic.com/wiki/EolExtension" target="_blank">http://mercurial.selenic.com/wiki/EolExtension</a><br>
.. _win32text extension: <a href="http://mercurial.selenic.com/wiki/Win32TextExtension" target="_blank">http://mercurial.selenic.com/wiki/Win32TextExtension</a><br>
_______________________________________________<br>
Python-checkins mailing list<br>
<a href="mailto:Python-checkins@python.org">Python-checkins@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/python-checkins" target="_blank">http://mail.python.org/mailman/listinfo/python-checkins</a><br>
</blockquote></div><br></div>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4