[Python-Dev] Re: Re Re: Recent PEP-8 change (Ivan Pozdeev)

On Thu, 2 Jul 2020 at 21:18, David Antonini wrote: > > No contention to the contrary, but as a routine, post-merge git history > rewrite, not a grand plan, from what I understand. David, When you post, you (or more likely your mail program) somehow adds the name of the author of the post that

[Python-Dev] Re: Re Re: Recent PEP-8 change (Ivan Pozdeev)

On Thu, Jul 2, 2020 at 7:55 PM Eric V. Smith wrote: > But this commit was to the peps repo, which has far fewer commits, one > branch, no tags, and only 10 PRs. So while it's still an issue, it's not as > big a deal as if we were talking about the cpython repo. > > I don't know how many forks

[Python-Dev] Re: Re Re: Recent PEP-8 change (Ivan Pozdeev)

On 7/2/2020 6:49 PM, Rémi Lapeyre wrote: Le 3 juil. 2020 à 00:32, Ivan Pozdeev via Python-Dev mailto:python-dev@python.org>> a écrit : Athttps://git-scm.com/book/en/v2/Git-Branching-Rebasing#_rebase_vs_merge, they say that the argument of whether to allow overwriting history in VCSes

[Python-Dev] Re: Re Re: Recent PEP-8 change (Ivan Pozdeev)

> Le 3 juil. 2020 à 00:32, Ivan Pozdeev via Python-Dev > a écrit : > > At https://git-scm.com/book/en/v2/Git-Branching-Rebasing#_rebase_vs_merge > , > they say that the argument of whether to allow overwriting history

[Python-Dev] Re: Re Re: Recent PEP-8 change (Ivan Pozdeev)

At https://git-scm.com/book/en/v2/Git-Branching-Rebasing#_rebase_vs_merge, they say that the argument of whether to allow overwriting history in VCSes stems from two opposing views on what a project's history should be. One is that is shall be a raw, unedited record of events as they happened;