Den 2010-09-14 20:14 skrev Stefano Lattarini: > On Tuesday 14 September 2010, Peter Rosin wrote: >> However, I have only updated tests/ar.test to cope with the new >> reality. So, a lot of tests (100?) are likely to fall over due to >> the new portability warnings. The reason is that I don't know on >> what branch I should base such an intrusive patch. > You mean a patch adding AM_PROG_AR into all the tests which now requires > it, right? I'd base that on msvc branch (in fact, I'd make it a squash-in > for your attached patch). >> I fear that such a patch, when merged elsewhere, will be incomplete > No big deal IMHO, we could resort to a fake merge in such case > (`git commit --amend' can also edit merge commits AFAIK), fixing > all the tests that need to be fixed. And there will be few of > them anyway IMO.
BTW, I forgot to ask before, but can you please point out such a fake merge, so that I can see what I should aim for? Cheers, Peter
