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/2011-November/114525.html below:

[Python-Dev] patch metadata - to use or not to use?

[Python-Dev] patch metadata - to use or not to use? [Python-Dev] patch metadata - to use or not to use?Dirkjan Ochtman dirkjan at ochtman.nl
Sat Nov 19 22:41:24 CET 2011
On Sat, Nov 19, 2011 at 20:41, Petri Lehtinen <petri at digip.org> wrote:
>> Generally speaking, it's more useful for the checkin metadata to
>> reflect who actually did the checkin, since that's the most useful
>> information for the tracker and buildbot integration.
>
> At least in git, the commit metadata contains both author and
> committer (at least if they differ). Maybe mercurial has this too?

It does not.

Personally, I find it more appropriate to have the original patch
author in the "official" metadata, mostly because I personally find it
very satisfying to see my name in the changelog on hgweb and the like.
My own experience with that makes me think that it's probably helpful
in engaging contributors.

Cheers,

Dirkjan
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