Showing content from http://mail.python.org/pipermail/python-dev/attachments/20080330/d492aba7/attachment.htm below:
<br><br><div class="gmail_quote">On Sun, Mar 30, 2008 at 5:16 PM, "Martin v. Löwis" <<a href="mailto:martin@v.loewis.de">martin@v.loewis.de</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">> Is there any easy way that the burden of trunk -> py3k<br>
> merging could be moved to the original committers of<br>
> the trunk patches?<br>
<br>
</div>I'm not sure I understand the question. If the committer<br>
of the original patch would do the merge himself, then<br>
certainly the burden would be on him, and that's an easy<br>
way.<br>
<br>
If you meant to say "an easy way to enforce...", then I<br>
cannot see how that could work, other than establishing<br>
that as a policy, and starting to revoke commit privileges<br>
to people who don't follow the policy.</blockquote><div>I think we could just ask politely and try it for a while. If things aren't working, we can reevaluate.<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
Rather than actually merging changes, one could start<br>
sending out messages automatically to committers who<br>
don't either merge or block their changes within 24 hours<br>
(or send a summary message every day to python-dev).</blockquote><div>Like above, let's try a little before we start setting up new infrastructure left and right. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
Regards,<br>
<font color="#888888">Martin<br>
<br>
<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Cheers,<br>Benjamin Peterson
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