Re: merging msvc in branch-1.11

2011-11-10 Thread Stefano Lattarini
On Thursday 10 November 2011, Peter Rosin wrote: > > I'm just not happy with how the commit graph looks (at least as shown by > gitk). > > I don't really know what to do about it, and I realize that the > topic branches are not the sole culprits, sorry for pointing the finger > at you... > > Some

Re: merging msvc in branch-1.11

2011-11-10 Thread Peter Rosin
Stefano Lattarini skrev 2011-11-10 12:30: > On Thursday 10 November 2011, Peter Rosin wrote: >> Stefano Lattarini skrev 2011-11-10 11:02: >>> In the meantime, removing some already-merged and now inactive branches >>> (e.g., `prove' and `remove-deansification') might simplify the situation >>> a bi

[FYI] Various merges: merged maint into branch-1.11, master and msvc

2011-11-10 Thread Stefano Lattarini
Merge branch 'maint' into branch-1.11, msvc and master * maint: tests: avoid a spurious failure of 'ltinit.test' MinGW tests: testsuite is now safe to run with dmake in parallel mode tests: fix spurious failures w.r.t. parallel make and colorization tests: fix spuri

Re: merging msvc in branch-1.11

2011-11-10 Thread Stefano Lattarini
On Thursday 10 November 2011, Peter Rosin wrote: > Stefano Lattarini skrev 2011-11-10 11:27: > > > [SNIP] > > > Attached is the patch I've pushed to remedy this situation. > > Hmmm, I'd argue that when -Wextra-portability has been *explicitly* > specified it is wrong for it to disappear into thin

Re: merging msvc in branch-1.11

2011-11-10 Thread Stefano Lattarini
On Thursday 10 November 2011, Peter Rosin wrote: > Stefano Lattarini skrev 2011-11-10 11:02: > > On Tuesday 08 November 2011, Peter Rosin wrote: > >> [dropping automake@] > >> > >> Stefano Lattarini skrev 2011-11-04 11:37: > >> > 2. Create a new public branch `msvc-for-1.11', based off of >

Re: merging msvc in branch-1.11

2011-11-10 Thread Peter Rosin
Stefano Lattarini skrev 2011-11-10 11:27: > On Tuesday 08 November 2011, Peter Rosin wrote: >> Peter Rosin skrev 2011-11-08 21:48: >> >>> msvc-for-1.11 seems to work ok here. Testsuite still running though. >> >> And it stumbled on extra-portability2.test for similar reasons as >> with ar-lib{3,4}.

Re: merging msvc in branch-1.11

2011-11-10 Thread Stefano Lattarini
On Tuesday 08 November 2011, Peter Rosin wrote: > Peter Rosin skrev 2011-11-08 21:48: > > > msvc-for-1.11 seems to work ok here. Testsuite still running though. > > And it stumbled on extra-portability2.test for similar reasons as > with ar-lib{3,4}.test but I'm not sure if the "sanity check" shou

Re: merging msvc in branch-1.11

2011-11-10 Thread Stefano Lattarini
On Tuesday 08 November 2011, Peter Rosin wrote: > [dropping automake@] > > Stefano Lattarini skrev 2011-11-04 11:37: > > >> 2. Create a new public branch `msvc-for-1.11', based off of > >> `msvc'. > >> > > I've instead based `msvc-for-1.11' on a merge of `branch-1.11' > > and `msvc'. > > T

Re: [FYI] {msvc} tests: various minor tweakings, mostly related to AM_PROG_AR

2011-11-10 Thread Stefano Lattarini
Hi Peter, thanks for the feedback. On Tuesday 08 November 2011, Peter Rosin wrote: > Stefano Lattarini skrev 2011-11-03 15:15: > > * tests/alloca.test: Adjust to new portability requirements due > > to the new AM_PROG_AR macro. > > * tests/discover.test: Likewise. > > * tests/libobj3.test: Likewis