A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2017-August/149102.html below:

[Python-Dev] bpo-5001: More-informative multiprocessing error messages (#3079)

[Python-Dev] bpo-5001: More-informative multiprocessing error messages (#3079) [Python-Dev] bpo-5001: More-informative multiprocessing error messages (#3079)Terry Reedy tjreedy at udel.edu
Thu Aug 31 17:46:55 EDT 2017
On 8/31/2017 3:27 PM, Brett Cannon wrote:
> 
> 
> On Wed, 30 Aug 2017 at 02:56 Paul Moore <p.f.moore at gmail.com 

>     do so to squash their PRs themselves. Personally, I'd prefer that as,
>     apart from admin activities like making sure the PR and issue number
>     references are present and correct, I think the original submitter has
>     a better chance of properly summarising the PR in the merged commit
>     message anyway.

My experience is different.

> So you would want a comment when the PR reaches "awaiting merge" with 
> instructions requesting the author do their own squash commit to 

My impression is that this makes the individual commits disappear.

> simplify the message for us?

Not me.

-- 
Terry Jan Reedy

More information about the Python-Dev mailing list

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