From: Gaius Mulley <gaiusmod2@gmail.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: libgm2: Remove 'autogen.sh'
Date: Thu, 11 May 2023 12:26:17 +0100 [thread overview]
Message-ID: <87fs83xg6e.fsf@debian> (raw)
In-Reply-To: <87a5yeapdt.fsf@euler.schwinge.homeip.net> (Thomas Schwinge's message of "Mon, 8 May 2023 16:06:54 +0200")
Thomas Schwinge <thomas@codesourcery.com> writes:
> Hi!
>
> On 2023-04-14T13:49:20+0100, Gaius Mulley via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>> Thomas Schwinge <thomas@codesourcery.com> writes:
>>> Separately, given that plain 'autoreconf' works, why have 'autogen.sh' at
>>> all?
>>
>> If autoreconf does the same as autogen.sh then yes this can be removed
>
> Pushed to master branch commit bd6dbdb196da5aa5c7354e0fc7b0a146237bcf8a
> "libgm2: Remove 'autogen.sh'".
>
>
>> (or its contents replaced with a call to autoreconf perhaps?),
>
> I didn't see any advantage in that.
>
>
> Grüße
> Thomas
thank you!
regards,
Gaius
prev parent reply other threads:[~2023-05-11 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 14:47 [PATCH v3 8/19] modula2 front end: libgm2 contents Gaius Mulley
2023-04-11 20:07 ` libgm2: Adjust 'autogen.sh' to 'ACLOCAL_AMFLAGS', and simplify (was: [PATCH v3 8/19] modula2 front end: libgm2 contents) Thomas Schwinge
2023-04-14 12:49 ` libgm2: Adjust 'autogen.sh' to 'ACLOCAL_AMFLAGS', and simplify Gaius Mulley
2023-05-08 14:06 ` libgm2: Remove 'autogen.sh' (was: libgm2: Adjust 'autogen.sh' to 'ACLOCAL_AMFLAGS', and simplify) Thomas Schwinge
2023-05-11 11:26 ` Gaius Mulley [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fs83xg6e.fsf@debian \
--to=gaiusmod2@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=thomas@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).