[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC] Merging testsuite-work into master
From: |
Stefano Lattarini |
Subject: |
Re: [RFC] Merging testsuite-work into master |
Date: |
Mon, 26 Dec 2011 23:09:13 +0100 |
On 12/23/2011 11:17 AM, Stefano Lattarini wrote:
> HI Jim.
>
> On 12/23/2011 11:04 AM, Jim Meyering wrote:
>> Stefano Lattarini wrote:
>>> Any objection to the idea of finally merging the testsuite-work branch back
>>> into master?
>>
>> No objection at all. Please do.
>>
> I'll still wait a couple of days to give Peter and Ralf a chance to chime in,
> if they want to.
>
> Thanks,
> Stefano
>
No further objection, so I've proceeded with the merge, and pushed.
Thanks,
Stefano
-*-*-
commit 6568eaae2dd2ca448fb2f499e2653d494f57c0a5
Merge: e335107 a3f66de
Author: Stefano Lattarini <address@hidden>
AuthorDate: Mon Dec 26 22:49:22 2011 +0100
Commit: Stefano Lattarini <address@hidden>
CommitDate: Mon Dec 26 22:49:22 2011 +0100
Merge branch 'testsuite-work' into master
At last!
Keeping the `master' and `testsuite-work' separated was becoming
quite artificial, since there is no way we are going to release
a 1.12 version of Automake that doesn't include the support for
the TAP test protocol and for user-defined test drivers -- which
are all implemented into the testsuite-work branch.
Moreover, keeping those two branches separated was causing more
maintenance and double-checking work than were warranted, was
making the automake git repository even more contorted, and, on
the top of all that, was actually *reducing coverage* by making
all the important changes in testsuite-work less visible (less
on-field testing by developers that routinely use bleeding edge
versions, less automated testing by services like Hydra/NixOS,
et cetera).