Re: New libtool maintainer

I just took a look at those. Good catches on the typos, I probably would not have noticed them just reading the script myself. Same thing with the M4 `[]' quoting issue ( classic pitfall ). I'll get these merged ASAP. For the non-Linux patches I can merge them, but I don't have personally have

Re: New libtool maintainer

Alex Ameen writes: > For the non-Linux patches I can merge them, but I don't have personally > have OSX, powerpc, or Solaris boxes, and while I do have a Windows > partition I don't currently have it set up to run these kinds of > tests. Nonetheless I can merge these - if you have access to any o

Re: New libtool maintainer

That would be a huge help. Thanks for the tip, I'm filling out the account request stuff now. :) On 11/21/21 2:04 PM, Russ Allbery wrote: Alex Ameen writes: For the non-Linux patches I can merge them, but I don't have personally have OSX, powerpc, or Solaris boxes, and while I do have a Wind

Re: New libtool maintainer

On Sun, 2021-11-21 at 13:14 -0600, Alex Ameen wrote: > I just took a look at those. Good catches on the typos, I probably would > not have noticed them just reading the script myself. Same thing with > the M4 `[]' quoting issue ( classic pitfall ). I'll get these merged ASAP. > > For the non-Lin

[sr #110550] File expected to be at /usr/bin/file, isn't on ChromeOS

Update of sr #110550 (project libtool): Status: Ready For Test => Done Open/Closed:Open => Closed ___ Reply to this item at:

[sr #110525] Typos caught by codespell

Update of sr #110525 (project libtool): Assigned to:None => growpotkin ___ Reply to this item at: ___