[Reviewers] [PATCH 1 of 2 V2] tests: use absolute_import and print_function in seq.py , test-ancestor.py

Kevin Bullock kbullock+mercurial at ringworld.org
Sat Apr 2 02:05:33 UTC 2016


> On Apr 1, 2016, at 13:38, Pierre-Yves David <pierre-yves.david at ens-lyon.org> wrote:
> 
> On 04/01/2016 07:56 AM, Yuya Nishihara wrote:
>> On Thu, 31 Mar 2016 19:15:26 +0300, Robert Stanca wrote:
>>> # HG changeset patch
>>> # User Robert Stanca <robert.stanca7 at gmail.com>
>>> # Date 1459436991 -10800
>>> #      Thu Mar 31 18:09:51 2016 +0300
>>> # Node ID 1aa23d597ac85bd8e53f92281a6251e58b9405d7
>>> # Parent  ff0d3b6b287f89594bd8d0308fe2810d2a18ea01
>>> tests: use absolute_import and print_function in seq.py , test-ancestor.py
>> 
>> To committers:
>> Should I split this into seq.py and test-ancestor.py patches?
> 
> We probably want to stick to the "one change per patch idea" one category of change and one file per patch.

(to reviewers only) Especially since this is probably a prospective GSoC student, whom we want to internalize our patch contribution standards as early as possible in the process.

pacem in terris / мир / शान्ति / ‎‫سَلاَم‬ / 平和
Kevin R. Bullock




More information about the Reviewers mailing list