> On 4 Feb 2019, at 11:58, Stephane Wirtel <stephane at wirtel.be> wrote: > > Hi all, > > After a git pull, I have seen there is a merge for v3.8.0a1 by Łukasz > Langa, why? I think the code should keep a linear commit and in this > case, it's against the "commit&squash" of CPython and Github :/ > > Thank you for your response. Tagging a release is different from a regular PR in the sense that you want the commit hash that you tagged as a given version to *remain the same*. In the mean time, other developers can (and will!) merge pull requests. If you were to rebase *the release tag* over their changes, the commit hash wouldn't match anymore. If you were to rebase *their changes* over your release tag, you'd have to force-push to update their changes. This is described in PEP 101. - Ł -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: Message signed with OpenPGP URL: <http://mail.python.org/pipermail/python-dev/attachments/20190204/673eae3c/attachment.sig>
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