* Stefano Lattarini wrote on Fri, Nov 05, 2010 at 09:21:28PM CET:
Nonetheless, there was still a potential bug (introduced by the merge)
lurking in there, which didn't manifest itself because, by sheer luck,
the Automake parallel test driver worked around it (by exporting
srcdir=$(srcdir) in
On Friday 05 November 2010, Stefano Lattarini wrote:
On Friday 05 November 2010, Stefano Lattarini wrote:
On Thursday 04 November 2010, Stefano Lattarini wrote:
In the end, are you OK with having me to merge test-init to
master right away, and do future testsuite work on master only?
On Thursday 04 November 2010, Stefano Lattarini wrote:
In the end, are you OK with having me to merge test-init to master right
away, and do future testsuite work on master only?
Yes.
Good.
I merged tests-init to master, fixed the resulting ChangeLog, and pushed.
(oh, and the testsuite
On Wednesday 03 November 2010, Ralf Wildenhues wrote:
* Stefano Lattarini wrote on Wed, Nov 03, 2010 at 02:27:47PM CET:
On Monday 01 November 2010, Ralf Wildenhues wrote:
I'm so totally behind on patches and not getting better, that the
strategy of ignoring testsuite work will not help
* Stefano Lattarini wrote on Thu, Nov 04, 2010 at 01:03:17PM CET:
On Wednesday 03 November 2010, Ralf Wildenhues wrote:
* Stefano Lattarini wrote on Wed, Nov 03, 2010 at 02:27:47PM CET:
Just one question: what about the already-existing tests-init branch?
Should I try to bring it to a
On Monday 01 November 2010, Ralf Wildenhues wrote:
Hi Stefano,
Hi Ralf, and thanks for bringing this up again.
I'm so totally behind on patches and not getting better, that the
strategy of ignoring testsuite work will not help either. So how about
the following. IIRC you suggested a branch
* Stefano Lattarini wrote on Wed, Nov 03, 2010 at 02:27:47PM CET:
On Monday 01 November 2010, Ralf Wildenhues wrote:
I'm so totally behind on patches and not getting better, that the
strategy of ignoring testsuite work will not help either. So how about
the following. IIRC you suggested a
Hi Stefano,
I'm so totally behind on patches and not getting better, that the
strategy of ignoring testsuite work will not help either. So how about
the following. IIRC you suggested a branch for low-danger testsuite
updates. I'm not sure if a single branch would always be the right
thing to
