Should non-security 2.7 bugs be fixed?

Terry Reedy tjreedy at udel.edu
Tue Jul 21 06:45:11 CEST 2015


On 7/20/2015 11:33 PM, Chris Angelico wrote:

> It's also the manner of workflow. If you want to accept patches and
> have them acknowledged to their original authors, the patches need to
> carry metadata identifying the authors. Notice how the patch files start straight in with content. There's no
> authorship information retained.
>
> By comparison, a patch created with 'git format-patch' and applied
> with 'git am' starts with RFC 822 headers, provides a commit message,
> and generally is intended as a way of transmitting a *commit*, rather
> than simply some changes. I'm not overly familiar with Mercurial
> workflows, but I think 'hg export' and 'hg import' give the same sort
> of information; I tried on CPython and got this:

hg has an option to produce git-format patches.  However, they do not 
work with the Rietveld code review tool, and so are discouraged.  I do 
not know if the extra information would survive an hg commit.

-- 
Terry Jan Reedy



More information about the Python-list mailing list