[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Extensions to M4sh
From: |
Zack Weinberg |
Subject: |
Re: Extensions to M4sh |
Date: |
Tue, 03 May 2022 16:35:37 -0400 |
User-agent: |
Cyrus-JMAP/3.7.0-alpha0-591-gfe6c3a2700-fm-20220427.001-gfe6c3a27 |
On Mon, May 2, 2022, at 2:30 AM, Paul Eggert wrote:
> On 5/1/22 19:06, Alex Ameen wrote:
>> Whoever is most
>> actively working on M4sh would be an incredibly useful contact for me, so
>> if "that's you" let me know.
>
> To be honest right now I think "that's you" is the correct answer. As
> in, you're the one.
I concur. Right now it seems like nobody is actively working on anything in
Autoconf, so if you've got patches that makes you the most active contributor.
I am probably the person who most recently _worked_ on m4sh and I would be
happy to review the patches you have.
> If these are extensions to m4sh (as opposed to changes) and would be
> useful outside libtool it sounds like Autoconf would be a good home for
> them, whatever they are.
The trickiest thing here is probably going to be release management. I
certainly wouldn't mind turning the crank on an autoconf 2.72 that just had the
m4sh improvements + whatever other patches have been committed since 2.71, if
that would make your life easier; however, presumably you don't want to make
libtool N+1 _require_ the hypothetical autoconf 2.72, so you will need to carry
the improvements yourself for a while, and we'll have to coordinate changes
between both copies.
zw
- Extensions to M4sh, Alex Ameen, 2022/05/01
- Re: Extensions to M4sh, Paul Eggert, 2022/05/02
- Re: Extensions to M4sh,
Zack Weinberg <=
- Re: Extensions to M4sh, Demi Marie Obenour, 2022/05/04
- Re: Extensions to M4sh, Michael Orlitzky, 2022/05/04
- Re: Extensions to M4sh, Nate Bargmann, 2022/05/04
- Re: Extensions to M4sh, Per Bothner, 2022/05/04
- Re: Extensions to M4sh, Michael Orlitzky, 2022/05/04
- Re: Extensions to M4sh, Carlos O'Donell, 2022/05/04
- Re: Extensions to M4sh, Carlos O'Donell, 2022/05/04