Showing content from http://mail.python.org/pipermail/python-dev/attachments/20180912/141cc433/attachment-0001.html below:
<div dir="auto"><div>It is still up to the core dev to set the message properly, but the HTML comments are invisible on GitHub until you edit the message. That bug is now fixed, though; HTML comments are stripped from the message before creating the commit.<br><br><div data-smartmail="gmail_signature">--<br>Zach<br>(Top-posted in HTML from a phone)</div><br><div class="gmail_quote"><div dir="ltr">On Wed, Sep 12, 2018, 01:34 Serhiy Storchaka <<a href="mailto:storchaka@gmail.com">storchaka@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">12.09.18 01:34, Miss Islington (bot) пиÑе:<br>
> <a href="https://github.com/python/cpython/commit/d13e59c1b512069d90efe7ee9b613d3913e79c56" rel="noreferrer noreferrer" target="_blank">https://github.com/python/cpython/commit/d13e59c1b512069d90efe7ee9b613d3913e79c56</a><br>
> commit: d13e59c1b512069d90efe7ee9b613d3913e79c56<br>
> branch: master<br>
> author: Benjamin Peterson <<a href="mailto:benjamin@python.org" target="_blank" rel="noreferrer">benjamin@python.org</a>><br>
> committer: Miss Islington (bot) <<a href="mailto:31488909%2Bmiss-islington@users.noreply.github.com" target="_blank" rel="noreferrer">31488909+miss-islington@users.noreply.github.com</a>><br>
> date: 2018-09-11T15:29:57-07:00<br>
> summary:<br>
> <br>
> Make sure the line comes from the same node as the col offset. (GH-9189)<br>
> <br>
> Followup to 90fc8980bbcc5c7dcced3627fe172b0bfd193a3b.<br>
> <br>
> <!--<br>
> Thanks for your contribution!<br>
> Please read this comment in its entirety. It's quite important.<br>
> <br>
> # Pull Request title<br>
> <br>
> It should be in the following format:<br>
> <br>
> ```<br>
> bpo-NNNN: Summary of the changes made<br>
> ```<br>
> <br>
> Where: bpo-NNNN refers to the issue number in the <a href="https://bugs.python.org" rel="noreferrer noreferrer" target="_blank">https://bugs.python.org</a>.<br>
> <br>
> Most PRs will require an issue number. Trivial changes, like fixing a typo, do not need an issue.<br>
> <br>
> # Backport Pull Request title<br>
> <br>
> If this is a backport PR (PR made against branches other than `master`),<br>
> please ensure that the PR title is in the following format:<br>
> <br>
> ```<br>
> [X.Y] <title from the original PR> (GH-NNNN)<br>
> ```<br>
> <br>
> Where: [X.Y] is the branch name, e.g. [3.6].<br>
> <br>
> GH-NNNN refers to the PR number from `master`.<br>
> <br>
> --><br>
<br>
This commit message looks awful (and it is duplicated in maintained <br>
branches). Please stop automerging to master by bots. The reason of <br>
automating merging before is that the core dev that performs merging is <br>
responsible for editing the commit message. There were mistakes from <br>
time to time, but usually regular commiters did care of this.<br>
<br>
I often use "git log", and such commit messages spoil the history.<br>
<br>
_______________________________________________<br>
Python-Dev mailing list<br>
<a href="mailto:Python-Dev@python.org" target="_blank" rel="noreferrer">Python-Dev@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/python-dev" rel="noreferrer noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/python-dev</a><br>
Unsubscribe: <a href="https://mail.python.org/mailman/options/python-dev/zachary.ware%2Bpydev%40gmail.com" rel="noreferrer noreferrer" target="_blank">https://mail.python.org/mailman/options/python-dev/zachary.ware%2Bpydev%40gmail.com</a><br>
</blockquote></div></div></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