From: Mike Frysinger <vapier@gentoo.org>
To: "R. Diez" <rdiezmail-newlib@yahoo.de>
Cc: newlib@sourceware.org
Subject: Re: require autoconf-2.69 exactly
Date: Wed, 12 Jan 2022 16:37:22 -0500 [thread overview]
Message-ID: <Yd9KErEUP2Ek+Lbj@vapier> (raw)
In-Reply-To: <81f7aca6-e34a-cfec-1181-001e0e00ea8a@yahoo.de>
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
i have no plans on fighting how gcc/binutils/gdb/etc... manage their autotools
integration. it's not what i do in any of my projects (i never commit any of
these generated files), but it's what the canonical toolchain projects have
opted to do, and newlib is part of that ecosystem.
i wish you all the best in convincing gcc/binutils/gdb/etc... to change their
ways ;).
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-01-12 21:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 18:39 newlib: require autoconf-2.69 Mike Frysinger
2022-01-05 12:10 ` Corinna Vinschen
2022-01-05 13:04 ` R. Diez
2022-01-06 1:46 ` Mike Frysinger
2022-01-06 6:10 ` Mike Frysinger
2022-01-07 9:58 ` Corinna Vinschen
2022-01-07 19:09 ` Mike Frysinger
2022-01-10 9:02 ` Corinna Vinschen
2022-01-11 0:58 ` Mike Frysinger
2022-01-11 10:23 ` Corinna Vinschen
2022-01-12 0:52 ` Mike Frysinger
2022-01-12 10:19 ` Corinna Vinschen
2022-01-12 17:24 ` Mike Frysinger
2022-01-07 9:56 ` Corinna Vinschen
2022-01-07 19:10 ` Mike Frysinger
2022-01-10 9:07 ` Corinna Vinschen
2022-01-12 18:24 ` require autoconf-2.69 exactly Mike Frysinger
2022-01-12 20:01 ` R. Diez
2022-01-12 21:37 ` Mike Frysinger [this message]
2022-01-14 10:12 ` Corinna Vinschen
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=Yd9KErEUP2Ek+Lbj@vapier \
--to=vapier@gentoo.org \
--cc=newlib@sourceware.org \
--cc=rdiezmail-newlib@yahoo.de \
/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).