Hi Peter, * Peter Rosin wrote on Thu, Aug 12, 2010 at 06:03:03PM CEST: > From 8c406f64b66aedee8359ddf1383e087faa2ba233 Mon Sep 17 00:00:00 2001 > From: Peter Rosin <p...@lysator.liu.se> > Date: Thu, 12 Aug 2010 18:01:18 +0200 > Subject: [PATCH] Enable the use of "link -lib" as the wrapped archiver. > > * lib/ar-lib: Enable the use of "link -lib" as the wrapped > archiver, as well as allowing some other options to be passed > through to the wrapped archiver. > * tests/ar-lib.test: Test the above. > > Signed-off-by: Peter Rosin <p...@lysator.liu.se>
This is ok for the msvc branch (which I just pushed to make it public). Thanks. I'd like to ask you to commit all approved msvc patches initially to the msvc branch, unless otherwise noted. You can also at any time you like merge the msvc branch to the master branch. Committing to msvc first allows us to still decide whether and when the branch should be merged to branch-1.11 (or maint, for that matter) as well, without dragging in the rest of master. If there will be commits that I think are good, but maybe not suitable for branch-1.11, we may want to split msvc in two branches, say with a new msvc-compat branch which then only holds those patches that are good for backporting. In that case merging from msvc-compat to msvc and from either to master is ok to do at any time. The general idea is that patches only involving 'ar-lib' and 'compile' in their public API are pretty much always good for 1.11 as well, but new API should go to 1.12 only. Cheers, Ralf
